All of lore.kernel.org
 help / color / mirror / Atom feed
From: pangzizhen001@208suo.com
To: oliver@neukum.org, aliakc@web.de, lenehan@twibble.org,
	jejb@linux.ibm.com, martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] drivers/scsi: Fix typos in comments
Date: Fri, 21 Jul 2023 00:06:11 +0800	[thread overview]
Message-ID: <0dbfe7a07c205bde3fc60408ce7aa55a@208suo.com> (raw)
In-Reply-To: <20230720160417.4434-1-wangjianli@cdjrlc.com>

Delete duplicate word "the"

Signed-off-by: Zizhen Pang <pangzizhen001@208suo.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 c8e86f8a631e..077e76407c58 100644
--- a/drivers/scsi/dc395x.c
+++ b/drivers/scsi/dc395x.c
@@ -2052,7 +2052,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
-         * the DMA FIFO to become empty? How do we know, that the 
device not already
+         * DMA FIFO to become empty? How do we know, that the device 
not already
           * sent data to the FIFO in a MsgIn phase, eg.?
           */
          if (!(DC395x_read8(acb, TRM_S1040_DMA_FIFOSTAT) & 0x80)) {

       reply	other threads:[~2023-07-20 16:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230720160417.4434-1-wangjianli@cdjrlc.com>
2023-07-20 16:06 ` pangzizhen001 [this message]
2023-07-21  4:00   ` [PATCH] drivers/scsi: Fix typos in comments Bagas Sanjaya

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=0dbfe7a07c205bde3fc60408ce7aa55a@208suo.com \
    --to=pangzizhen001@208suo.com \
    --cc=aliakc@web.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.