driver core: minor comment formatting cleanups
authorGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 8 Mar 2012 20:20:37 +0000 (12:20 -0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 8 Mar 2012 20:20:37 +0000 (12:20 -0800)
Came in in the deferred probe patch, quick, clean them up before a
kernel janitor finds them and sends me 4 individual patches to fix them
up...

Cc: Grant Likely <grant.likely@secretlab.ca>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/base/dd.c

index 9fa888e080592e045b3efba21386a9ba2b9c40a1..1b1cbb571d38d72acce854b8fc6437b5323783c9 100644 (file)
@@ -80,8 +80,10 @@ static void deferred_probe_work_func(struct work_struct *work)
 
                get_device(dev);
 
-               /* Drop the mutex while probing each device; the probe path
-                * may manipulate the deferred list */
+               /*
+                * Drop the mutex while probing each device; the probe path may
+                * manipulate the deferred list
+                */
                mutex_unlock(&deferred_probe_mutex);
                dev_dbg(dev, "Retrying from deferred list\n");
                bus_probe_device(dev);
@@ -126,16 +128,20 @@ static void driver_deferred_probe_trigger(void)
        if (!driver_deferred_probe_enable)
                return;
 
-       /* A successful probe means that all the devices in the pending list
+       /*
+        * A successful probe means that all the devices in the pending list
         * should be triggered to be reprobed.  Move all the deferred devices
-        * into the active list so they can be retried by the workqueue */
+        * into the active list so they can be retried by the workqueue
+        */
        mutex_lock(&deferred_probe_mutex);
        list_splice_tail_init(&deferred_probe_pending_list,
                              &deferred_probe_active_list);
        mutex_unlock(&deferred_probe_mutex);
 
-       /* Kick the re-probe thread.  It may already be scheduled, but
-        * it is safe to kick it again. */
+       /*
+        * Kick the re-probe thread.  It may already be scheduled, but it is
+        * safe to kick it again.
+        */
        queue_work(deferred_wq, &deferred_probe_work);
 }
 
@@ -171,8 +177,10 @@ static void driver_bound(struct device *dev)
 
        klist_add_tail(&dev->p->knode_driver, &dev->driver->p->klist_devices);
 
-       /* Make sure the device is no longer in one of the deferred lists
-        * and kick off retrying all pending devices */
+       /*
+        * Make sure the device is no longer in one of the deferred lists and
+        * kick off retrying all pending devices
+        */
        driver_deferred_probe_del(dev);
        driver_deferred_probe_trigger();