From: Zhang Jiaming <jiaming@nfschina.com>
To: jejb@linux.ibm.com, martin.petersen@oracle.com
Cc: bvanassche@acm.org, johannes.thumshirn@wdc.com,
himanshu.madhani@oracle.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, liqiong@nfschina.com,
renyu@nfschina.com, Zhang Jiaming <jiaming@nfschina.com>
Subject: [PATCH] scsi: csiostor: Fix some typos in comments
Date: Fri, 1 Jul 2022 18:41:30 +0800 [thread overview]
Message-ID: <20220701104130.24644-1-jiaming@nfschina.com> (raw)
There are some typos in /drivers/scsi/csiostor/csio_scsi.c.
Fix it.
Signed-off-by: Zhang Jiaming <jiaming@nfschina.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
reply other threads:[~2022-07-01 10:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220701104130.24644-1-jiaming@nfschina.com \
--to=jiaming@nfschina.com \
--cc=bvanassche@acm.org \
--cc=himanshu.madhani@oracle.com \
--cc=jejb@linux.ibm.com \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=liqiong@nfschina.com \
--cc=martin.petersen@oracle.com \
--cc=renyu@nfschina.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
all inboxes | Powered by JetHome®