From: "Rangankar, Manish" <Manish.Rangankar@cavium.com>
To: Colin King <colin.king@canonical.com>,
Dept-Eng QLogic Storage Upstream
<QLogic-Storage-Upstream@cavium.com>,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scsi: qedi: fix another spelling mistake: "alloction" -> "allocation"
Date: Mon, 3 Jul 2017 10:30:32 +0000 [thread overview]
Message-ID: <D5801A6D.3B20F%manish.rangankar@cavium.com> (raw)
In-Reply-To: <20170703102402.12853-1-colin.king@canonical.com>
On 03/07/17 3:54 PM, "Colin King" <colin.king@canonical.com> wrote:
>From: Colin Ian King <colin.king@canonical.com>
>
>Trivial fix to spelling mistake in QEDF_ERR message. I should have
>also included this in a previous fix, but I only just spotted this one.
>
>Signed-off-by: Colin Ian King <colin.king@canonical.com>
>---
> drivers/scsi/qedi/qedi_fw.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/drivers/scsi/qedi/qedi_fw.c b/drivers/scsi/qedi/qedi_fw.c
>index 19254bd739d9..93d54acd4a22 100644
>--- a/drivers/scsi/qedi/qedi_fw.c
>+++ b/drivers/scsi/qedi/qedi_fw.c
>@@ -1411,7 +1411,7 @@ static void qedi_tmf_work(struct work_struct *work)
>
> list_work = kzalloc(sizeof(*list_work), GFP_ATOMIC);
> if (!list_work) {
>- QEDI_ERR(&qedi->dbg_ctx, "Memory alloction failed\n");
>+ QEDI_ERR(&qedi->dbg_ctx, "Memory allocation failed\n");
> goto abort_ret;
> }
>
>--
>2.11.0
>
Thanks
Acked-by: Manish Rangankar <Manish.Rangankar@cavium.com>
next prev parent reply other threads:[~2017-07-03 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 10:24 Colin King
2017-07-03 10:30 ` Rangankar, Manish [this message]
2017-07-12 21:11 ` 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=D5801A6D.3B20F%manish.rangankar@cavium.com \
--to=manish.rangankar@cavium.com \
--cc=QLogic-Storage-Upstream@cavium.com \
--cc=colin.king@canonical.com \
--cc=jejb@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome