USB kernel-doc fixes
Subsystems (2)
PATCH 1/3 USB kernel-doc fixes
From: Randy Dunlap <[email protected]>
Fix kernel-doc warnings and errors in USB.
Signed-off-by Randy Dunlap <[email protected]>
--- Documentation/DocBook/gadget.tmpl | 4 ++-- Documentation/DocBook/usb.tmpl | 6 +++--- drivers/usb/core/driver.c | 1 + 3 files changed, 6 insertions(+), 5 deletions(-)
Documentation/DocBook/usb.tmpl +3 -3
@@ -187,13 +187,13 @@ <chapter><title>USB-Standard Types</title> - <para>In <filename><linux/usb_ch9.h></filename> you will find + <para>In <filename><linux/usb/ch9.h></filename> you will find the USB data types defined in chapter 9 of the USB specification. These data types are used throughout USB, and in APIs including this host side API, gadget APIs, and usbfs. </para> -!Iinclude/linux/usb_ch9.h +!Iinclude/linux/usb/ch9.h </chapter>
@@ -574,7 +574,7 @@ for (;;) { #include <asm/byteorder.h></programlisting> The standard USB device model requests, from "Chapter 9" of the USB 2.0 specification, are automatically included from - the <filename><linux/usb_ch9.h></filename> header. + the <filename><linux/usb/ch9.h></filename> header. </para> <para>Unless noted otherwise, the ioctl requests
Documentation/DocBook/gadget.tmpl +2 -2
@@ -482,13 +482,13 @@ slightly. <para>Gadget drivers rely on common USB structures and constants defined in the -<filename><linux/usb_ch9.h></filename> +<filename><linux/usb/ch9.h></filename> header file, which is standard in Linux 2.6 kernels. These are the same types and constants used by host side drivers (and usbcore). </para> -!Iinclude/linux/usb_ch9.h +!Iinclude/linux/usb/ch9.h </sect1> <sect1 id="core"><title>Core Objects and Methods</title>
drivers/usb/core/driver.c +1 -0
@@ -743,6 +743,7 @@ EXPORT_SYMBOL_GPL(usb_deregister_device_* usb_register_driver - register a USB interface driver * @new_driver: USB operations for the interface driver * @owner: module owner of this driver. +* @mod_name: module name string * * Registers a USB interface driver with the USB core. The list of * unattached interfaces will be rescanned whenever a new driver is