diff options
| author | Mauro Carvalho Chehab <mchehab@s-opensource.com> | 2017-04-05 10:23:12 -0300 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2017-04-11 14:40:48 -0600 |
| commit | e0c34e900611a58c93adf463d096c5843eb1967a (patch) | |
| tree | 8232218145228258caa76bb97b99bf2123b202e9 | |
| parent | 69966c94b95832d51e7fbaa0e31a0ed5534c48e6 (diff) | |
| download | blackbird-op-linux-e0c34e900611a58c93adf463d096c5843eb1967a.tar.gz blackbird-op-linux-e0c34e900611a58c93adf463d096c5843eb1967a.zip | |
usb: get rid of some ReST doc build errors
We need an space before a numbered list to avoid those warnings:
./drivers/usb/core/message.c:478: ERROR: Unexpected indentation.
./drivers/usb/core/message.c:479: WARNING: Block quote ends without a blank line; unexpected unindent.
./include/linux/usb/composite.h:455: ERROR: Unexpected indentation.
./include/linux/usb/composite.h:456: WARNING: Block quote ends without a blank line; unexpected unindent.
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>
| -rw-r--r-- | drivers/usb/core/message.c | 1 | ||||
| -rw-r--r-- | include/linux/usb/composite.h | 1 |
2 files changed, 2 insertions, 0 deletions
diff --git a/drivers/usb/core/message.c b/drivers/usb/core/message.c index 2184ef40a82a..4c38ea41ae96 100644 --- a/drivers/usb/core/message.c +++ b/drivers/usb/core/message.c @@ -474,6 +474,7 @@ EXPORT_SYMBOL_GPL(usb_sg_init); * significantly improve USB throughput. * * There are three kinds of completion for this function. + * * (1) success, where io->status is zero. The number of io->bytes * transferred is as requested. * (2) error, where io->status is a negative errno value. The number diff --git a/include/linux/usb/composite.h b/include/linux/usb/composite.h index 4616a49a1c2e..30a063e98c19 100644 --- a/include/linux/usb/composite.h +++ b/include/linux/usb/composite.h @@ -451,6 +451,7 @@ static inline struct usb_composite_driver *to_cdriver( * sure doing that won't hurt too much. * * One notion for how to handle Wireless USB devices involves: + * * (a) a second gadget here, discovery mechanism TBD, but likely * needing separate "register/unregister WUSB gadget" calls; * (b) updates to usb_gadget to include flags "is it wireless", |
