diff options
| author | Mauro Carvalho Chehab <mchehab@s-opensource.com> | 2017-04-05 10:23:11 -0300 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2017-04-11 14:40:37 -0600 |
| commit | 69966c94b95832d51e7fbaa0e31a0ed5534c48e6 (patch) | |
| tree | fbeb90cd1815b1d22ac64e17fc1cf6d7969abb65 /Documentation/driver-api | |
| parent | e463c06335d04043c079f1d1d66472ec049de5dd (diff) | |
| download | linux-69966c94b95832d51e7fbaa0e31a0ed5534c48e6.tar.gz linux-69966c94b95832d51e7fbaa0e31a0ed5534c48e6.tar.bz2 linux-69966c94b95832d51e7fbaa0e31a0ed5534c48e6.zip | |
usb.rst: get rid of some Sphinx errors
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>
Diffstat (limited to 'Documentation/driver-api')
| -rw-r--r-- | Documentation/driver-api/usb/usb.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/driver-api/usb/usb.rst b/Documentation/driver-api/usb/usb.rst index d15ab8ae5239..5ebaf669704c 100644 --- a/Documentation/driver-api/usb/usb.rst +++ b/Documentation/driver-api/usb/usb.rst @@ -615,8 +615,8 @@ USBDEVFS_CONTROL 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 for details. The bRequestType value is composed by combining a - USB_TYPE_\* value, a USB_DIR_\* value, and a USB_RECIP_\* - value (from *<linux/usb.h>*). If wLength is nonzero, it describes + ``USB_TYPE_*`` value, a ``USB_DIR_*`` value, and a ``USB_RECIP_*`` + value (from ``linux/usb.h``). If wLength is nonzero, it describes the length of the data buffer, which is either written to the device (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 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, and a user "context" value serving to uniquely identify each request. (It's usually a pointer to per-request data.) Flags can modify requests |