public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] driver core: cleanup double words comments
@ 2022-02-12 14:32 trix
  0 siblings, 0 replies; only message in thread
From: trix @ 2022-02-12 14:32 UTC (permalink / raw)
  To: gregkh, rafael; +Cc: linux-kernel, Tom Rix

From: Tom Rix <trix@redhat.com>

Remove the second 'are' and 'the'.

Signed-off-by: Tom Rix <trix@redhat.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


^ permalink raw reply related	[flat|nested] only message in thread

only message in thread, other threads:[~2022-02-12 14:33 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-02-12 14:32 [PATCH] driver core: cleanup double words comments trix

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox