linux-kernel - [PATCH] scsi: csiostor: Fix some typos in comments

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <20220701104130.24644-1-jiaming@nfschina.com>
Date:   Fri,  1 Jul 2022 18:41:30 +0800
From:   Zhang Jiaming <jiaming@...china.com>
To:     jejb@...ux.ibm.com, martin.petersen@...cle.com
Cc:     bvanassche@....org, johannes.thumshirn@....com,
        himanshu.madhani@...cle.com, linux-scsi@...r.kernel.org,
        linux-kernel@...r.kernel.org, liqiong@...china.com,
        renyu@...china.com, Zhang Jiaming <jiaming@...china.com>
Subject: [PATCH] scsi: csiostor: Fix some typos in comments

There are some typos in /drivers/scsi/csiostor/csio_scsi.c.
Fix it.

Signed-off-by: Zhang Jiaming <jiaming@...china.com>
---
 drivers/scsi/csiostor/csio_scsi.c | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/drivers/scsi/csiostor/csio_scsi.c b/drivers/scsi/csiostor/csio_scsi.c
index 9aafe0002ab1..a3dc6cc33136 100644
--- a/drivers/scsi/csiostor/csio_scsi.c
+++ b/drivers/scsi/csiostor/csio_scsi.c
@@ -153,7 +153,7 @@ csio_scsi_itnexus_loss_error(uint16_t error)
 }
 
 /*
- * csio_scsi_fcp_cmnd - Frame the SCSI FCP command paylod.
+ * csio_scsi_fcp_cmnd - Frame the SCSI FCP command payload.
  * @req: IO req structure.
  * @addr: DMA location to place the payload.
  *
@@ -782,7 +782,7 @@ csio_scsis_io_active(struct csio_ioreq *req, enum csio_scsi_ev evt)
 		list_del_init(&req->sm.sm_list);
 		csio_set_state(&req->sm, csio_scsis_uninit);
 		/*
-		 * In MSIX mode, with multiple queues, the SCSI compeltions
+		 * In MSIX mode, with multiple queues, the SCSI completions
 		 * could reach us sooner than the FW events sent to indicate
 		 * I-T nexus loss (link down, remote device logo etc). We
 		 * dont want to be returning such I/Os to the upper layer
@@ -943,7 +943,7 @@ csio_scsis_aborting(struct csio_ioreq *req, enum csio_scsi_ev evt)
 		 * 5. FW couldn't genuinely abort the request for some reason,
 		 *    and sent us an error.
 		 *
-		 * The first 3 scenarios are treated as  succesful abort
+		 * The first 3 scenarios are treated as  successful abort
 		 * operations by the host, while the last 2 are failed attempts
 		 * to abort. Manipulate the return value of the request
 		 * appropriately, so that host can convey these results
@@ -1018,7 +1018,7 @@ csio_scsis_closing(struct csio_ioreq *req, enum csio_scsi_ev evt)
 
 		/*
 		 * Either close succeeded, or we issued close to FW at the
-		 * same time FW compelted it to us. Either way, the I/O
+		 * same time FW completed it to us. Either way, the I/O
 		 * is closed.
 		 */
 		CSIO_DB_ASSERT((req->wr_status == FW_SUCCESS) ||
@@ -2010,7 +2010,7 @@ csio_eh_abort_handler(struct scsi_cmnd *cmnd)
  * @req: IO request.
  *
  * Cache the result in 'cmnd', since ioreq will be freed soon
- * after we return from here, and the waiting thread shouldnt trust
+ * after we return from here, and the waiting thread shouldn't trust
  * the ioreq contents.
  */
 static void
-- 
2.25.1