From: wangjianli <wangjianli@cdjrlc.com>
To: oliver@neukum.org, aliakc@web.de, lenehan@twibble.org,
jejb@linux.ibm.com, martin.petersen@oracle.com
Cc: dc395x@twibble.org, linux-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:45:35 +0800 [thread overview]
Message-ID: <20221022064535.34616-1-wangjianli@cdjrlc.com> (raw)
Delete the redundant word 'the'.
Signed-off-by: wangjianli <wangjianli@cdjrlc.com>
---
drivers/scsi/dc395x.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/dc395x.c b/drivers/scsi/dc395x.c
index 670a836a6ba1..a7db373d5e2c 100644
--- a/drivers/scsi/dc395x.c
+++ b/drivers/scsi/dc395x.c
@@ -2051,7 +2051,7 @@ static void data_in_phase0(struct AdapterCtlBlk *acb, struct ScsiReqBlk *srb,
}
/*
* KG: We should wait for the DMA FIFO to be empty ...
- * but: it would be better to wait first for the SCSI FIFO and then the
+ * but: it would be better to wait first for the SCSI FIFO and then
* the DMA FIFO to become empty? How do we know, that the device not already
* sent data to the FIFO in a MsgIn phase, eg.?
*/
--
2.36.1
next reply other threads:[~2022-10-22 6:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 6:45 wangjianli [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-22 6:28 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=20221022064535.34616-1-wangjianli@cdjrlc.com \
--to=wangjianli@cdjrlc.com \
--cc=aliakc@web.de \
--cc=dc395x@twibble.org \
--cc=jejb@linux.ibm.com \
--cc=lenehan@twibble.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=oliver@neukum.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
all inboxes | Powered by JetHome®