From: William Theesfeld <william@theesfeld.net>
To: Justin Tee <justin.tee@broadcom.com>
Cc: Paul Ely <paul.ely@broadcom.com>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] scsi: lpfc: fix spelling mistake in comment
Date: Mon, 1 Jun 2026 16:20:01 -0400 [thread overview]
Message-ID: <20260601202001.651088-1-william@theesfeld.net> (raw)
Comment-only change. No functional impact.
Signed-off-by: William Theesfeld <william@theesfeld.net>
---
drivers/scsi/lpfc/lpfc_bsg.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/lpfc/lpfc_bsg.c b/drivers/scsi/lpfc/lpfc_bsg.c
index 7406dfa60..2b87dbe3f 100644
--- a/drivers/scsi/lpfc/lpfc_bsg.c
+++ b/drivers/scsi/lpfc/lpfc_bsg.c
@@ -5003,7 +5003,7 @@ lpfc_bsg_issue_mbox(struct lpfc_hba *phba, struct bsg_job *job,
} else if (phba->sli_rev == LPFC_SLI_REV4) {
/* Let type 4 (well known data) through because the data is
* returned in varwords[4-8]
- * otherwise check the recieve length and fetch the buffer addr
+ * otherwise check the receive length and fetch the buffer addr
*/
if ((pmb->mbxCommand == MBX_DUMP_MEMORY) &&
(pmb->un.varDmp.type != DMP_WELL_KNOWN)) {
--
2.54.0
next reply other threads:[~2026-06-01 20:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 20:20 William Theesfeld [this message]
2026-06-01 22:10 ` [PATCH] scsi: lpfc: fix spelling mistake in comment Justin Tee
2026-06-02 11:19 ` [PATCH v2] scsi: lpfc: fix spelling mistakes in comments William Theesfeld
2026-06-02 18:12 ` Justin Tee
2026-06-08 21:47 ` Martin K. Petersen
2026-06-16 2:26 ` Martin K. Petersen
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=20260601202001.651088-1-william@theesfeld.net \
--to=william@theesfeld.net \
--cc=James.Bottomley@HansenPartnership.com \
--cc=justin.tee@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=paul.ely@broadcom.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