Skip to content

Commit be816bc

Browse files
committed
Documentation:ipmi: Remove comments about interrupt level
Callbacks no longer run at interrupt level or bh, so remove those comments. Signed-off-by: Corey Minyard <cminyard@mvista.com>
1 parent 6bd0eb6 commit be816bc

File tree

1 file changed

+3
-6
lines changed

1 file changed

+3
-6
lines changed

Documentation/driver-api/ipmi.rst

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -280,10 +280,8 @@ Creating the User
280280
To use the message handler, you must first create a user using
281281
ipmi_create_user. The interface number specifies which SMI you want
282282
to connect to, and you must supply callback functions to be called
283-
when data comes in. The callback function can run at interrupt level,
284-
so be careful using the callbacks. This also allows to you pass in a
285-
piece of data, the handler_data, that will be passed back to you on
286-
all calls.
283+
when data comes in. This also allows to you pass in a piece of data,
284+
the handler_data, that will be passed back to you on all calls.
287285

288286
Once you are done, call ipmi_destroy_user() to get rid of the user.
289287

@@ -303,8 +301,7 @@ use it for anything you like.
303301

304302
Responses come back in the function pointed to by the ipmi_recv_hndl
305303
field of the "handler" that you passed in to ipmi_create_user().
306-
Remember again, these may be running at interrupt level. Remember to
307-
look at the receive type, too.
304+
Remember to look at the receive type, too.
308305

309306
From userland, you fill out an ipmi_req_t structure and use the
310307
IPMICTL_SEND_COMMAND ioctl. For incoming stuff, you can use select()

0 commit comments

Comments
 (0)