From 3066fa910caf0916fe7cf3eb6c5f9aa5320855e8 Mon Sep 17 00:00:00 2001 From: David Brownell Date: Mon, 8 Apr 2002 00:05:16 -0700 Subject: USB kerneldoc fixes This fixes some kerneldoc bugs for USB. It catches up with the recent rename, and includes a couple minor tweaks/fixes I happened to notice. --- include/linux/usb.h | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'include/linux') diff --git a/include/linux/usb.h b/include/linux/usb.h index 2b7b4d39b590..828cf3f50846 100644 --- a/include/linux/usb.h +++ b/include/linux/usb.h @@ -471,8 +471,10 @@ struct usb_device_id { /** * struct usb_driver - identifies USB driver to usbcore - * @owner: pointer to the module owner of this driver - * @name: The driver name should be unique among USB drivers + * @owner: Pointer to the module owner of this driver; initialize + * it using THIS_MODULE. + * @name: The driver name should be unique among USB drivers, + * and should normally be the same as the module name. * @probe: Called to see if the driver is willing to manage a particular * interface on a device. The probe routine returns a handle that * will later be provided to disconnect(), or a null pointer to @@ -507,7 +509,7 @@ struct usb_device_id { * is used by both user and kernel mode hotplugging support. * * The probe() and disconnect() methods are called in a context where - * they can sleep, but they should avoid abusing the privilage. Most + * they can sleep, but they should avoid abusing the privilege. Most * work to connect to a device should be done when the device is opened, * and undone at the last close. The disconnect code needs to address * concurrency issues with respect to open() and close() methods, as -- cgit v1.2.3