All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhang Jiaming <jiaming@nfschina.com>
To: jejb@linux.ibm.com, martin.petersen@oracle.com,
	anil.gurumurthy@qlogic.com, sudarsana.kalluru@qlogic.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	liqiong@nfschina.com, renyu@nfschina.com,
	Zhang Jiaming <jiaming@nfschina.com>
Subject: [PATCH] scsi: bfa: Fix spelling mistake
Date: Wed, 29 Jun 2022 14:56:07 +0800	[thread overview]
Message-ID: <20220629065607.24213-1-jiaming@nfschina.com> (raw)

Change 'Mangement' to 'Management'.
Change 'paramater' to 'parameter'.

Signed-off-by: Zhang Jiaming <jiaming@nfschina.com>
---
 drivers/scsi/bfa/bfa_fc.h | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/scsi/bfa/bfa_fc.h b/drivers/scsi/bfa/bfa_fc.h
index 0314e4b9e1fb..8f4573c48bf2 100644
--- a/drivers/scsi/bfa/bfa_fc.h
+++ b/drivers/scsi/bfa/bfa_fc.h
@@ -218,8 +218,8 @@ enum {
 	FC_ELS_FAN = 0x60,	/* Fabric Address Notification */
 	FC_ELS_RSCN = 0x61,	/* Reg State Change Notification */
 	FC_ELS_SCR = 0x62,	/* State Change Registration. */
-	FC_ELS_RTIN = 0x77,	/* Mangement server request */
-	FC_ELS_RNID = 0x78,	/* Mangement server request */
+	FC_ELS_RTIN = 0x77,	/* Management server request */
+	FC_ELS_RNID = 0x78,	/* Management server request */
 	FC_ELS_RLIR = 0x79,	/* Registered Link Incident Record */
 
 	FC_ELS_RPSC = 0x7D,	/* Report Port Speed Capabilities */
@@ -462,7 +462,7 @@ struct fc_rsi_s {
 };
 
 /*
- * structure for PRLI paramater pages, both request & response
+ * structure for PRLI parameter pages, both request & response
  * see FC-PH-X table 113 & 115 for explanation also FCP table 8
  */
 struct fc_prli_params_s {
-- 
2.34.1


                 reply	other threads:[~2022-06-29  6:56 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=20220629065607.24213-1-jiaming@nfschina.com \
    --to=jiaming@nfschina.com \
    --cc=anil.gurumurthy@qlogic.com \
    --cc=jejb@linux.ibm.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 \
    --cc=sudarsana.kalluru@qlogic.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.