From: Sumit Saxena <sumit.saxena@broadcom.com>
To: Colin King <colin.king@canonical.com>,
Kashyap Desai <kashyap.desai@broadcom.com>,
Shivasharan Srikanteshwara
<shivasharan.srikanteshwara@broadcom.com>,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
"PDL,MEGARAIDLINUX" <megaraidlinux.pdl@broadcom.com>
Cc: linux-kernel@vger.kernel.org
Subject: RE: [PATCH][V2] scsi: megaraid_sas: fix spelling mistakes: "oustanding" -> "outstanding"
Date: Thu, 4 May 2017 16:53:35 +0530 [thread overview]
Message-ID: <7f977651fb0cae857efde247d76d004e@mail.gmail.com> (raw)
In-Reply-To: <20170429221051.12087-1-colin.king@canonical.com>
>-----Original Message-----
>From: Colin King [mailto:colin.king@canonical.com]
>Sent: Sunday, April 30, 2017 3:41 AM
>To: Kashyap Desai; Sumit Saxena; Shivasharan S; James E . J . Bottomley;
>Martin K . Petersen; megaraidlinux.pdl@broadcom.com
>Cc: linux-kernel@vger.kernel.org
>Subject: [PATCH][V2] scsi: megaraid_sas: fix spelling mistakes:
"oustanding"
>-> "outstanding"
>
>From: Colin Ian King <colin.king@canonical.com>
>
>trivial fix to spelling mistakes in dev_info and scmd_printk messages.
Also
>join lines on split literal string to clean up checkpatch warning.
>
>Signed-off-by: Colin Ian King <colin.king@canonical.com>
>---
> drivers/scsi/megaraid/megaraid_sas_base.c | 2 +-
> drivers/scsi/megaraid/megaraid_sas_fusion.c | 3 +--
> 2 files changed, 2 insertions(+), 3 deletions(-)
>
>diff --git a/drivers/scsi/megaraid/megaraid_sas_base.c
>b/drivers/scsi/megaraid/megaraid_sas_base.c
>index 316c3df0c3fd..0a9478fdb58b 100644
>--- a/drivers/scsi/megaraid/megaraid_sas_base.c
>+++ b/drivers/scsi/megaraid/megaraid_sas_base.c
>@@ -2638,7 +2638,7 @@ static int megasas_wait_for_outstanding(struct
>megasas_instance *instance)
> do {
> if ((fw_state == MFI_STATE_FAULT) ||
>atomic_read(&instance->fw_outstanding)) {
> dev_info(&instance->pdev->dev,
>- "%s:%d waiting_for_outstanding: before
>issue OCR. FW state = 0x%x, oustanding 0x%x\n",
>+ "%s:%d waiting_for_outstanding: before
>issue OCR. FW state = 0x%x,
>+outstanding 0x%x\n",
> __func__, __LINE__, fw_state,
>atomic_read(&instance->fw_outstanding));
> if (i == 3)
> goto kill_hba_and_failed;
>diff --git a/drivers/scsi/megaraid/megaraid_sas_fusion.c
>b/drivers/scsi/megaraid/megaraid_sas_fusion.c
>index f990ab4d45e1..adba9f450dec 100644
>--- a/drivers/scsi/megaraid/megaraid_sas_fusion.c
>+++ b/drivers/scsi/megaraid/megaraid_sas_fusion.c
>@@ -3975,8 +3975,7 @@ int megasas_task_abort_fusion(struct scsi_cmnd
>*scmd)
>
> if (!smid) {
> ret = SUCCESS;
>- scmd_printk(KERN_NOTICE, scmd, "Command for which
>abort is"
>- " issued is not found in oustanding commands\n");
>+ scmd_printk(KERN_NOTICE, scmd, "Command for which
>abort is issued is
>+not found in outstanding commands\n");
> mutex_unlock(&instance->reset_mutex);
> goto out;
> }
Acked-by: Sumit Saxena <sumit.saxena@broadcom.com>
>--
>2.11.0
prev parent reply other threads:[~2017-05-04 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 22:10 [PATCH][V2] scsi: megaraid_sas: fix spelling mistakes: "oustanding" -> "outstanding" Colin King
2017-05-04 11:23 ` Sumit Saxena [this message]
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=7f977651fb0cae857efde247d76d004e@mail.gmail.com \
--to=sumit.saxena@broadcom.com \
--cc=colin.king@canonical.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=kashyap.desai@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=megaraidlinux.pdl@broadcom.com \
--cc=shivasharan.srikanteshwara@broadcom.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).