From: Jilin Yuan <yuanjilin@cdjrlc.com>
To: b-liu@ti.com, gregkh@linuxfoundation.org
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Jilin Yuan <yuanjilin@cdjrlc.com>
Subject: [PATCH] usb/musb: fix repeated words in comments
Date: Sat, 16 Jul 2022 21:44:57 +0800 [thread overview]
Message-ID: <20220716134457.46535-1-yuanjilin@cdjrlc.com> (raw)
Delete the redundant word 'mode'.
Delete the redundant word 'than'.
Signed-off-by: Jilin Yuan <yuanjilin@cdjrlc.com>
---
drivers/usb/musb/musb_cppi41.c | 2 +-
drivers/usb/musb/tusb6010.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/musb/musb_cppi41.c b/drivers/usb/musb/musb_cppi41.c
index 7fbb8a307145..c963cb8565f2 100644
--- a/drivers/usb/musb/musb_cppi41.c
+++ b/drivers/usb/musb/musb_cppi41.c
@@ -286,7 +286,7 @@ static void cppi41_dma_callback(void *private_data,
* receive a FIFO empty interrupt so the only thing we can do is
* to poll for the bit. On HS it usually takes 2us, on FS around
* 110us - 150us depending on the transfer size.
- * We spin on HS (no longer than than 25us and setup a timer on
+ * We spin on HS (no longer than 25us and setup a timer on
* FS to check for the bit and complete the transfer.
*/
if (is_host_active(musb)) {
diff --git a/drivers/usb/musb/tusb6010.c b/drivers/usb/musb/tusb6010.c
index 7ed4cc348d99..5609b4e84d40 100644
--- a/drivers/usb/musb/tusb6010.c
+++ b/drivers/usb/musb/tusb6010.c
@@ -495,7 +495,7 @@ static void musb_do_idle(struct timer_list *t)
}
/*
- * Maybe put TUSB6010 into idle mode mode depending on USB link status,
+ * Maybe put TUSB6010 into idle mode depending on USB link status,
* like "disconnected" or "suspended". We'll be woken out of it by
* connect, resume, or disconnect.
*
--
2.36.1
next reply other threads:[~2022-07-16 13:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 13:44 Jilin Yuan [this message]
2022-08-21 15:30 [PATCH] usb/musb: fix repeated words in comments Jilin Yuan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220716134457.46535-1-yuanjilin@cdjrlc.com \
--to=yuanjilin@cdjrlc.com \
--cc=b-liu@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).