summaryrefslogtreecommitdiff
path: root/drivers/base/dd.c
diff options
context:
space:
mode:
authorShailendra Verma <shailendra.capricorn@gmail.com>2015-05-25 21:16:11 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2015-06-01 04:15:17 +0300
commit9ba8af66432cb8e82553f2e273eb11db0cec7d2d (patch)
tree34ed545a8d662d49aea795fa276bb0a958ee8851 /drivers/base/dd.c
parent6d9d4b1469b0d9748145e168fc9ec585e1f3f4b0 (diff)
downloadlinux-9ba8af66432cb8e82553f2e273eb11db0cec7d2d.tar.xz
base:dd - Fix for typo in comment to function driver_deferred_probe_trigger().
Signed-off-by: Shailendra Verma <shailendra.capricorn@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/base/dd.c')
-rw-r--r--drivers/base/dd.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/base/dd.c b/drivers/base/dd.c
index 8da8e071f01d..a638bbb1a27a 100644
--- a/drivers/base/dd.c
+++ b/drivers/base/dd.c
@@ -141,7 +141,7 @@ static bool driver_deferred_probe_enable = false;
* more than one device is probing at the same time, it is possible for one
* probe to complete successfully while another is about to defer. If the second
* depends on the first, then it will get put on the pending list after the
- * trigger event has already occured and will be stuck there.
+ * trigger event has already occurred and will be stuck there.
*
* The atomic 'deferred_trigger_count' is used to determine if a successful
* trigger has occurred in the midst of probing a driver. If the trigger count