lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Date:   Sat, 22 Oct 2022 14:45:35 +0800
From:   wangjianli <wangjianli@...rlc.com>
To:     oliver@...kum.org, aliakc@....de, lenehan@...bble.org,
        jejb@...ux.ibm.com, martin.petersen@...cle.com
Cc:     dc395x@...bble.org, linux-scsi@...r.kernel.org,
        linux-kernel@...r.kernel.org, wangjianli <wangjianli@...rlc.com>
Subject: [PATCH] drivers/scsi: fix repeated words in comments

Delete the redundant word 'the'.

Signed-off-by: wangjianli <wangjianli@...rlc.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ