linux-kernel - Re: [PATCH][next] scsi: lpfc: fix spelling mistake "Notication" -> "Notification"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 21 Feb 2020 09:42:03 -0800
From:   James Smart <james.smart@...adcom.com>
To:     Colin King <colin.king@...onical.com>,
        Dick Kennedy <dick.kennedy@...adcom.com>,
        "James E . J . Bottomley" <jejb@...ux.ibm.com>,
        "Martin K . Petersen" <martin.petersen@...cle.com>,
        linux-scsi@...r.kernel.org
Cc:     kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH][next] scsi: lpfc: fix spelling mistake "Notication" ->
 "Notification"



On 2/21/2020 7:48 AM, Colin King wrote:
> From: Colin Ian King <colin.king@...onical.com>
>
> There is a spelling mistake in a lpfc_printf_vlog info messgae. Fix it.
>
> Signed-off-by: Colin Ian King <colin.king@...onical.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@...adcom.com>

Thanks!

-- james