diff options
| author | Mauro Carvalho Chehab <mchehab@s-opensource.com> | 2017-04-05 10:23:15 -0300 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2017-04-11 14:41:29 -0600 |
| commit | e1c3e6e1ca996e0403a5958c054d2cebf1642b15 (patch) | |
| tree | f7b29c76c6fe49d8e54d0538ad033635fc124ba6 /Documentation/driver-api/usb/callbacks.rst | |
| parent | 0cb300623e3bb460fd9853bbde2fd1973e3bbcd8 (diff) | |
docs-rst: fix usb cross-references
As some USB documentation files got moved, adjust their
cross-references to their new place.
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/usb/callbacks.rst')
| -rw-r--r-- | Documentation/driver-api/usb/callbacks.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/driver-api/usb/callbacks.rst b/Documentation/driver-api/usb/callbacks.rst index 93a8d53e27e7..2b80cf54bcc3 100644 --- a/Documentation/driver-api/usb/callbacks.rst +++ b/Documentation/driver-api/usb/callbacks.rst @@ -8,7 +8,7 @@ Usbcore will call into a driver through callbacks defined in the driver structure and through the completion handler of URBs a driver submits. Only the former are in the scope of this document. These two kinds of callbacks are completely independent of each other. Information on the -completion callback can be found in Documentation/usb/URB.txt. +completion callback can be found in :ref:`usb-urb`. The callbacks defined in the driver structure are: @@ -53,7 +53,7 @@ The callbacks defined in the driver structure are: The ioctl interface (2) should be used only if you have a very good reason. Sysfs is preferred these days. The PM callbacks are covered -separately in Documentation/usb/power-management.txt. +separately in :ref:`usb-power-management`. Calling conventions =================== |