[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20220212143233.2648872-1-trix@redhat.com>
Date: Sat, 12 Feb 2022 06:32:33 -0800
From: trix@...hat.com
To: gregkh@...uxfoundation.org, rafael@...nel.org
Cc: linux-kernel@...r.kernel.org, Tom Rix <trix@...hat.com>
Subject: [PATCH] driver core: cleanup double words comments
From: Tom Rix <trix@...hat.com>
Remove the second 'are' and 'the'.
Signed-off-by: Tom Rix <trix@...hat.com>
---
drivers/base/dd.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/base/dd.c b/drivers/base/dd.c
index 9eaaff2f556c..1a4113b3b3b9 100644
--- a/drivers/base/dd.c
+++ b/drivers/base/dd.c
@@ -835,7 +835,7 @@ struct device_attach_data {
struct device *dev;
/*
- * Indicates whether we are are considering asynchronous probing or
+ * Indicates whether we are considering asynchronous probing or
* not. Only initial binding after device or driver registration
* (including deferral processing) may be done asynchronously, the
* rest is always synchronous, as we expect it is being done by
@@ -1039,7 +1039,7 @@ static void __device_driver_lock(struct device *dev, struct device *parent)
* @parent: Parent device. Needed if the bus requires parent lock
*
* This function will release the required locks for manipulating dev->drv.
- * Normally this will just be the the @dev lock, but when called for a
+ * Normally this will just be the @dev lock, but when called for a
* USB interface, @parent lock will be released as well.
*/
static void __device_driver_unlock(struct device *dev, struct device *parent)
--
2.26.3
Powered by blists - more mailing lists