From: James Smart <james.smart@broadcom.com>
To: Colin King <colin.king@canonical.com>,
Dick Kennedy <dick.kennedy@broadcom.com>,
"James E . J . Bottomley" <jejb@linux.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] scsi: lpfc: fix spelling mistake "Notication" -> "Notification"
Date: Fri, 21 Feb 2020 09:42:03 -0800 [thread overview]
Message-ID: <db8a57f5-53e3-08ea-048f-8b5dca08b16e@broadcom.com> (raw)
In-Reply-To: <20200221154841.77791-1-colin.king@canonical.com>
On 2/21/2020 7:48 AM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake in a lpfc_printf_vlog info messgae. Fix it.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/scsi/lpfc/lpfc_els.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/lpfc/lpfc_els.c b/drivers/scsi/lpfc/lpfc_els.c
> index a712f15bc88c..80d1e661b0d4 100644
> --- a/drivers/scsi/lpfc/lpfc_els.c
> +++ b/drivers/scsi/lpfc/lpfc_els.c
> @@ -3128,7 +3128,7 @@ lpfc_cmpl_els_disc_cmd(struct lpfc_hba *phba, struct lpfc_iocbq *cmdiocb,
> for (i = 0; i < ELS_RDF_REG_TAG_CNT &&
> i < be32_to_cpu(prdf->reg_d1.reg_desc.count); i++)
> lpfc_printf_vlog(vport, KERN_INFO, LOG_ELS,
> - "4677 Fabric RDF Notication Grant Data: "
> + "4677 Fabric RDF Notification Grant Data: "
> "0x%08x\n",
> be32_to_cpu(
> prdf->reg_d1.desc_tags[i]));
Reviewed-by: James Smart <james.smart@broadcom.com>
Thanks!
-- james
next prev parent reply other threads:[~2020-02-21 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 15:48 [PATCH][next] scsi: lpfc: fix spelling mistake "Notication" -> "Notification" Colin King
2020-02-21 17:42 ` James Smart [this message]
2020-02-24 20:18 ` 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=db8a57f5-53e3-08ea-048f-8b5dca08b16e@broadcom.com \
--to=james.smart@broadcom.com \
--cc=colin.king@canonical.com \
--cc=dick.kennedy@broadcom.com \
--cc=jejb@linux.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).