Commit 93758098 authored by Dominik Kuhlen's avatar Dominik Kuhlen Committed by Greg Kroah-Hartman

[PATCH] fix USB documentation bug

USB fix documentation bug

 After some source investigations I discovered a harmless mistake:
 The description of the  usb_control_msg(...) function says
 it returns 0, or less than 0 if an error occured, but
 the usb_internal_control_msg returns length, which is sometimes >0
 (success) or <0 if error.
parent 934b1882
...@@ -1182,7 +1182,7 @@ int usb_internal_control_msg(struct usb_device *usb_dev, unsigned int pipe, ...@@ -1182,7 +1182,7 @@ int usb_internal_control_msg(struct usb_device *usb_dev, unsigned int pipe,
* This function sends a simple control message to a specified endpoint * This function sends a simple control message to a specified endpoint
* and waits for the message to complete, or timeout. * and waits for the message to complete, or timeout.
* *
* If successful, it returns 0, otherwise a negative error number. * If successful, it returns the number of bytes transferred, otherwise a negative error number.
* *
* Don't use this function from within an interrupt context, like a * Don't use this function from within an interrupt context, like a
* bottom half handler. If you need an asynchronous message, or need to send * bottom half handler. If you need an asynchronous message, or need to send
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment