All of lore.kernel.org
 help / color / mirror / Atom feed
From: lijian_8010a29@163.com
To: james.smart@broadcom.com, dick.kennedy@broadcom.com,
	jejb@linux.ibm.com, martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	lijian <lijian@yulong.com>
Subject: [PATCH] scsi: lpfc: lpfc_nvmet: deleted the repeated word
Date: Tue,  8 Jun 2021 15:21:33 +0800	[thread overview]
Message-ID: <20210608072133.272091-1-lijian_8010a29@163.com> (raw)

From: lijian <lijian@yulong.com>

deleted the repeated word 'the' and 'received' in the comments.

Signed-off-by: lijian <lijian@yulong.com>
---
 drivers/scsi/lpfc/lpfc_nvmet.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/scsi/lpfc/lpfc_nvmet.c b/drivers/scsi/lpfc/lpfc_nvmet.c
index f2d9a3580887..bf35984e58e9 100644
--- a/drivers/scsi/lpfc/lpfc_nvmet.c
+++ b/drivers/scsi/lpfc/lpfc_nvmet.c
@@ -1469,7 +1469,7 @@ lpfc_nvmet_cleanup_io_context(struct lpfc_hba *phba)
 	if (!infop)
 		return;
 
-	/* Cycle the the entire CPU context list for every MRQ */
+	/* Cycle the entire CPU context list for every MRQ */
 	for (i = 0; i < phba->cfg_nvmet_mrq; i++) {
 		for_each_present_cpu(j) {
 			infop = lpfc_get_ctx_list(phba, j, i);
@@ -3562,7 +3562,7 @@ lpfc_nvmet_unsol_fcp_issue_abort(struct lpfc_hba *phba,
  * lpfc_nvme_unsol_ls_issue_abort - issue ABTS on an exchange received
  *        via async frame receive where the frame is not handled.
  * @phba: pointer to adapter structure
- * @ctxp: pointer to the asynchronously received received sequence
+ * @ctxp: pointer to the asynchronously received sequence
  * @sid: address of the remote port to send the ABTS to
  * @xri: oxid value to for the ABTS (other side's exchange id).
  **/
-- 
2.25.1



             reply	other threads:[~2021-06-08  7:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08  7:21 lijian_8010a29 [this message]
2021-06-08 16:23 ` [PATCH] scsi: lpfc: lpfc_nvmet: deleted the repeated word James Smart

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=20210608072133.272091-1-lijian_8010a29@163.com \
    --to=lijian_8010a29@163.com \
    --cc=dick.kennedy@broadcom.com \
    --cc=james.smart@broadcom.com \
    --cc=jejb@linux.ibm.com \
    --cc=lijian@yulong.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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 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.