diff options
author | Tom Rix <trix@redhat.com> | 2022-02-12 06:32:33 -0800 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2022-02-22 08:16:05 +0100 |
commit | b4ae8c2fb673d2fc60cb8fe645dba4f4db8b0dab (patch) | |
tree | dddcc0920cd59fc60e7fe775fec78223b655e98a | |
parent | f3a690227f07390b0cfccb96ebbd87bf4ab0a5b2 (diff) | |
download | linux-b4ae8c2fb673d2fc60cb8fe645dba4f4db8b0dab.tar.bz2 |
driver core: cleanup double words comments
Remove the second 'are' and 'the'.
Signed-off-by: Tom Rix <trix@redhat.com>
Link: https://lore.kernel.org/r/20220212143233.2648872-1-trix@redhat.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-rw-r--r-- | drivers/base/dd.c | 4 |
1 files 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) |