From: Mukesh Ojha <mojha@codeaurora.org>
To: Colin King <colin.king@canonical.com>,
QLogic-Storage-Upstream@cavium.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] scsi: qedi: fix spelling mistake "oflload" -> "offload"
Date: Thu, 18 Apr 2019 11:29:31 +0530 [thread overview]
Message-ID: <071b73b2-424d-0bb0-a663-c63ee0a94425@codeaurora.org> (raw)
In-Reply-To: <20190417134304.10979-1-colin.king@canonical.com>
On 4/17/2019 7:13 PM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There are a couple of spelling mistakes in some kernel alert messages.
> Fix these.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Reviewed-by: Mukesh Ojha <mojha@codeaurora.org>
Cheers,
-Mukesh
> ---
> drivers/scsi/qedi/qedi_iscsi.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/scsi/qedi/qedi_iscsi.c b/drivers/scsi/qedi/qedi_iscsi.c
> index 6d6d6013e35b..e4391ee2c27a 100644
> --- a/drivers/scsi/qedi/qedi_iscsi.c
> +++ b/drivers/scsi/qedi/qedi_iscsi.c
> @@ -579,7 +579,7 @@ static int qedi_conn_start(struct iscsi_cls_conn *cls_conn)
> rval = qedi_iscsi_update_conn(qedi, qedi_conn);
> if (rval) {
> iscsi_conn_printk(KERN_ALERT, conn,
> - "conn_start: FW oflload conn failed.\n");
> + "conn_start: FW offload conn failed.\n");
> rval = -EINVAL;
> goto start_err;
> }
> @@ -590,7 +590,7 @@ static int qedi_conn_start(struct iscsi_cls_conn *cls_conn)
> rval = iscsi_conn_start(cls_conn);
> if (rval) {
> iscsi_conn_printk(KERN_ALERT, conn,
> - "iscsi_conn_start: FW oflload conn failed!!\n");
> + "iscsi_conn_start: FW offload conn failed!!\n");
> }
>
> start_err:
next prev parent reply other threads:[~2019-04-18 5:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 13:43 [PATCH] scsi: qedi: fix spelling mistake "oflload" -> "offload" Colin King
2019-04-18 4:24 ` Manish Rangankar
2019-04-18 5:59 ` Mukesh Ojha [this message]
2019-04-19 0:34 ` 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=071b73b2-424d-0bb0-a663-c63ee0a94425@codeaurora.org \
--to=mojha@codeaurora.org \
--cc=QLogic-Storage-Upstream@cavium.com \
--cc=colin.king@canonical.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).