From: wangjianli <wangjianli@cdjrlc.com>
To: fthain@linux-m68k.org, schmitzmic@gmail.com, jejb@linux.ibm.com,
martin.petersen@oracle.com
Cc: inux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
wangjianli <wangjianli@cdjrlc.com>
Subject: [PATCH] drivers/scsi: fix repeated words in comments
Date: Sat, 22 Oct 2022 14:28:09 +0800 [thread overview]
Message-ID: <20221022062809.16538-1-wangjianli@cdjrlc.com> (raw)
Delete the redundant word 'the'.
Signed-off-by: wangjianli <wangjianli@cdjrlc.com>
---
drivers/scsi/NCR5380.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/NCR5380.c b/drivers/scsi/NCR5380.c
index dece7d9eb4d3..36f8133ad7d8 100644
--- a/drivers/scsi/NCR5380.c
+++ b/drivers/scsi/NCR5380.c
@@ -857,7 +857,7 @@ static void NCR5380_dma_complete(struct Scsi_Host *instance)
* Checking for bus reset by reading RST is futile because of interrupt
* latency, but a bus reset will reset chip logic. Checking for parity error
* is unnecessary because that interrupt is never enabled. A Loss of BSY
- * condition will clear DMA Mode. We can tell when this occurs because the
+ * condition will clear DMA Mode. We can tell when this occurs because
* the Busy Monitor interrupt is enabled together with DMA Mode.
*/
--
2.36.1
next reply other threads:[~2022-10-22 6:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 6:28 wangjianli [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-22 6:45 [PATCH] drivers/scsi: fix repeated words in comments wangjianli
2022-09-08 13:07 wangjianli
2022-09-23 10:43 ` Wei Liu
2022-09-08 12:27 wangjianli
2022-09-08 12:24 wangjianli
2022-09-08 12:32 ` Conor.Dooley
2022-08-21 15:27 wangjianli
2022-07-24 7:27 wangjianli
2022-07-24 7:25 wangjianli
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=20221022062809.16538-1-wangjianli@cdjrlc.com \
--to=wangjianli@cdjrlc.com \
--cc=fthain@linux-m68k.org \
--cc=inux-scsi@vger.kernel.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=schmitzmic@gmail.com \
/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).