redonkable/freescale-linux-fslc
redonkable/freescale-linux-fslc
1
0
Fork 0
Code Releases Activity

usb.rst: get rid of some Sphinx errors

Browse source 
Get rid of those warnings:

    Documentation/driver-api/usb/usb.rst:615: ERROR: Unknown target name: "usb_type".
    Documentation/driver-api/usb/usb.rst:615: ERROR: Unknown target name: "usb_dir".
    Documentation/driver-api/usb/usb.rst:615: ERROR: Unknown target name: "usb_recip".
    Documentation/driver-api/usb/usb.rst:679: ERROR: Unknown target name: "usbdevfs_urb_type".

Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
Mauro Carvalho Chehab 2017-04-05 10:23:11 -03:00 committed by Jonathan Corbet
parent e463c06335
commit 69966c94b9
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
Documentation/driver-api/usb/usb.rst
View file

@ -615,8 +615,8 @@ USBDEVFS_CONTROL
The first eight bytes of this structure are the contents of the The first eight bytes of this structure are the contents of the
SETUP packet to be sent to the device; see the USB 2.0 specification SETUP packet to be sent to the device; see the USB 2.0 specification
for details. The bRequestType value is composed by combining a for details. The bRequestType value is composed by combining a
USB_TYPE_\* value, a USB_DIR_\* value, and a USB_RECIP_\* ``USB_TYPE_*`` value, a ``USB_DIR_*`` value, and a ``USB_RECIP_*``
value (from *<linux/usb.h>*). If wLength is nonzero, it describes value (from ``linux/usb.h``). If wLength is nonzero, it describes
the length of the data buffer, which is either written to the device the length of the data buffer, which is either written to the device
(USB_DIR_OUT) or read from the device (USB_DIR_IN). (USB_DIR_OUT) or read from the device (USB_DIR_IN).
@ -678,7 +678,7 @@ the blocking is separate.
These requests are packaged into a structure that resembles the URB used These requests are packaged into a structure that resembles the URB used
by kernel device drivers. (No POSIX Async I/O support here, sorry.) It by kernel device drivers. (No POSIX Async I/O support here, sorry.) It
identifies the endpoint type (USBDEVFS_URB_TYPE_\*), endpoint identifies the endpoint type (``USBDEVFS_URB_TYPE_*``), endpoint
(number, masked with USB_DIR_IN as appropriate), buffer and length, (number, masked with USB_DIR_IN as appropriate), buffer and length,
and a user "context" value serving to uniquely identify each request. and a user "context" value serving to uniquely identify each request.
(It's usually a pointer to per-request data.) Flags can modify requests (It's usually a pointer to per-request data.) Flags can modify requests