path: root/Documentation
diff options
authorAndrea Gelmini <>2010-05-23 21:56:42 +0200
committerGreg Kroah-Hartman <>2010-08-10 14:35:34 -0700
commitb03dbffdcf7903ae3f1e2d61887462301752d060 (patch)
treee075ef39c3d7c8604ad145fb2c369db058136a29 /Documentation
parent254217d1a86f80981e6dfc54d7412931c6f6e80b (diff)
USB: Documentation/usb/hotplug.txt: Checkpatch cleanup
Documentation/usb/hotplug.txt:13: ERROR: trailing whitespace Documentation/usb/hotplug.txt:87: ERROR: trailing whitespace Signed-off-by: Andrea Gelmini <> Signed-off-by: Greg Kroah-Hartman <>
Diffstat (limited to 'Documentation')
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/usb/hotplug.txt b/Documentation/usb/hotplug.txt
index f53170665f37..4c945716a660 100644
--- a/Documentation/usb/hotplug.txt
+++ b/Documentation/usb/hotplug.txt
@@ -10,7 +10,7 @@ immediately usable. That means the system must do many things, including:
- Bind a driver to that device. Bus frameworks do that using a
device driver's probe() routine.
- Tell other subsystems to configure the new device. Print
queues may need to be enabled, networks brought up, disk
partitions mounted, and so on. In some cases these will
@@ -84,7 +84,7 @@ USB MODUTILS SUPPORT
Current versions of module-init-tools will create a "modules.usbmap" file
which contains the entries from each driver's MODULE_DEVICE_TABLE. Such
files can be used by various user mode policy agents to make sure all the
-right driver modules get loaded, either at boot time or later.
+right driver modules get loaded, either at boot time or later.
See <linux/usb.h> for full information about such table entries; or look
at existing drivers. Each table entry describes one or more criteria to