base:dd - Fix for typo in comment to function driver_deferred_probe_trigger().
authorShailendra Verma <shailendra.capricorn@gmail.com>
Mon, 25 May 2015 18:16:11 +0000 (23:46 +0530)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Mon, 1 Jun 2015 01:15:17 +0000 (10:15 +0900)
Signed-off-by: Shailendra Verma <shailendra.capricorn@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/base/dd.c

index 8da8e071f01d37302851e3cf2f5833d916496b68..a638bbb1a27a573f7d959c20d459c73a368e8794 100644 (file)
@@ -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