From: Kashyap Desai <kashyap.desai@broadcom.com>
To: Bart Van Assche <bart.vanassche@sandisk.com>,
Colin King <colin.king@canonical.com>,
Sumit Saxena <sumit.saxena@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>,
linux-scsi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Sasikumar PC <sasikumar.pc@broadcom.com>,
Kiran Kumar Kasturi <kiran-kumar.kasturi@broadcom.com>
Subject: RE: [PATCH][V2] scsi: megaraid-sas: fix spelling mistake of "outstanding"
Date: Wed, 30 Nov 2016 10:47:03 +0530 [thread overview]
Message-ID: <0224a6a40ed0aaebfa88d9a82aae5125@mail.gmail.com> (raw)
In-Reply-To: <99f3f833-6dd6-557a-2ae4-0051dfbe9f36@sandisk.com>
> -----Original Message-----
> From: Bart Van Assche [mailto:bart.vanassche@sandisk.com]
> Sent: Wednesday, November 30, 2016 12:50 AM
> To: Colin King; Kashyap Desai; Sumit Saxena; Shivasharan S; James E . J .
> Bottomley; Martin K . Petersen; megaraidlinux.pdl@broadcom.com; linux-
> scsi@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: [PATCH][V2] scsi: megaraid-sas: fix spelling mistake of
> "outstanding"
>
> On 11/29/2016 11:13 AM, Colin King wrote:
> > Trivial fix to spelling mistake "oustanding" to "outstanding" in
> > dev_info and scmd_printk messages. Also join wrapped literal string in
> > the scmd_printk.
>
> Reviewed-by: Bart Van Assche <bart.vanassche@sandisk.com>
Please hold this commit as we have patch set work in progress for MegaRaid
Driver. It will conflict it this patch commits.
We will be re-submitting this patch with appropriate Signed-off and
Submitted-by tags.
Thanks, Kashyap
prev parent reply other threads:[~2016-11-30 5:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 19:13 [PATCH][V2] scsi: megaraid-sas: fix spelling mistake of "outstanding" Colin King
2016-11-29 19:20 ` Bart Van Assche
2016-11-30 5:17 ` Kashyap Desai [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=0224a6a40ed0aaebfa88d9a82aae5125@mail.gmail.com \
--to=kashyap.desai@broadcom.com \
--cc=bart.vanassche@sandisk.com \
--cc=colin.king@canonical.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=kiran-kumar.kasturi@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=megaraidlinux.pdl@broadcom.com \
--cc=sasikumar.pc@broadcom.com \
--cc=shivasharan.srikanteshwara@broadcom.com \
--cc=sumit.saxena@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).