---

yaml
---
r: 207953
b: refs/heads/master
c: b03dbff
h: refs/heads/master
i:
  207951: 578e898
v: v3

[refs]

@@ -1,2 +1,2 @@
 ---
-refs/heads/master: 254217d1a86f80981e6dfc54d7412931c6f6e80b
+refs/heads/master: b03dbffdcf7903ae3f1e2d61887462301752d060

trunk/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