diff options
| author | Jeremiah Mahler <jmmahler@gmail.com> | 2014-06-06 12:29:17 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-07-09 16:05:42 -0700 |
| commit | 31e01f0aca3e9b77fea0b1c1b569b02fa2812eb6 (patch) | |
| tree | 329a15f202be464724d7c4943d71ad19d91fbf63 | |
| parent | 14ad5a94cbf49399e3bc5262428df07f7c3a75c7 (diff) | |
| download | op-kernel-dev-31e01f0aca3e9b77fea0b1c1b569b02fa2812eb6.zip op-kernel-dev-31e01f0aca3e9b77fea0b1c1b569b02fa2812eb6.tar.gz | |
usb: doc: hotplug.txt code typos
Fixed several typos in the code examples given in
Documentation/usb/hotplug.txt.
- missing [] with array of struct usb_device_id
- checkpatch.pl warning: space between function name and parenthesis
- missing terminating ';'
Signed-off-by: Jeremiah Mahler <jmmahler@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| -rw-r--r-- | Documentation/usb/hotplug.txt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/usb/hotplug.txt b/Documentation/usb/hotplug.txt index 6424b13..a80b0e9 100644 --- a/Documentation/usb/hotplug.txt +++ b/Documentation/usb/hotplug.txt @@ -105,13 +105,13 @@ macros such as these, and use driver_info to store more information. A short example, for a driver that supports several specific USB devices and their quirks, might have a MODULE_DEVICE_TABLE like this: - static const struct usb_device_id mydriver_id_table = { + static const struct usb_device_id mydriver_id_table[] = { { USB_DEVICE (0x9999, 0xaaaa), driver_info: QUIRK_X }, { USB_DEVICE (0xbbbb, 0x8888), driver_info: QUIRK_Y|QUIRK_Z }, ... { } /* end with an all-zeroes entry */ - } - MODULE_DEVICE_TABLE (usb, mydriver_id_table); + }; + MODULE_DEVICE_TABLE(usb, mydriver_id_table); Most USB device drivers should pass these tables to the USB subsystem as well as to the module management subsystem. Not all, though: some driver @@ -134,7 +134,7 @@ something like this: if exposing any operations through usbdevfs: .ioctl = my_ioctl, */ - } + }; When the USB subsystem knows about a driver's device ID table, it's used when choosing drivers to probe(). The thread doing new device processing checks |
