Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

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: Jiri Kosina <jkosina@suse.cz>

authored by

Jeremiah Mahler and committed by
Jiri Kosina
429a91db 8740e687

+4 -4
+4 -4
Documentation/usb/hotplug.txt
··· 105 105 A short example, for a driver that supports several specific USB devices 106 106 and their quirks, might have a MODULE_DEVICE_TABLE like this: 107 107 108 - static const struct usb_device_id mydriver_id_table = { 108 + static const struct usb_device_id mydriver_id_table[] = { 109 109 { USB_DEVICE (0x9999, 0xaaaa), driver_info: QUIRK_X }, 110 110 { USB_DEVICE (0xbbbb, 0x8888), driver_info: QUIRK_Y|QUIRK_Z }, 111 111 ... 112 112 { } /* end with an all-zeroes entry */ 113 - } 114 - MODULE_DEVICE_TABLE (usb, mydriver_id_table); 113 + }; 114 + MODULE_DEVICE_TABLE(usb, mydriver_id_table); 115 115 116 116 Most USB device drivers should pass these tables to the USB subsystem as 117 117 well as to the module management subsystem. Not all, though: some driver ··· 134 134 if exposing any operations through usbdevfs: 135 135 .ioctl = my_ioctl, 136 136 */ 137 - } 137 + }; 138 138 139 139 When the USB subsystem knows about a driver's device ID table, it's used when 140 140 choosing drivers to probe(). The thread doing new device processing checks