From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: sasha.levin@oracle.com,
Luis Henriques <luis.henriques@canonical.com>,
Greg KH <gregkh@linuxfoundation.org>
Cc: linux-scsi@vger.kernel.org, JBottomley@Odin.com,
alexng@microsoft.com, LKML <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
devel@linuxdriverproject.org,
Haiyang Zhang <haiyangz@microsoft.com>
Subject: Re: [PATCH][v3.18.y][3.19.y-ckt][4.0.y] storvsc: Set the SRB flags correctly when no data transfer is, needed
Date: Fri, 05 Jun 2015 13:59:24 -0400 [thread overview]
Message-ID: <5571E37C.1070900@canonical.com> (raw)
In-Reply-To: <5571E19C.9000202@canonical.com>
On 06/05/2015 01:51 PM, Joseph Salisbury wrote:
> Hello,
>
> Please consider including mainline commit
> dc45708ca9988656d706940df5fd102672c5de92 in the next v3.18.y, v4.0.y and
> 3.19.y-ckt stable releases. It was
> included in the mainline tree as of v4.1-rc5. It has been tested and
> confirmed to resolve the following bug:
> http://bugs.launchpad.net/bugs/1439780
>
> commit dc45708ca9988656d706940df5fd102672c5de92
> Author: K. Y. Srinivasan <kys@microsoft.com>
> Date: Fri May 1 11:03:02 2015 -0700
>
> storvsc: Set the SRB flags correctly when no data transfer is needed
>
>
>
> Sincerely,
>
> Joseph Salisbury
>
>
It looks like this commit was already cc'd to stable. Sorry for the noise.
Thanks,
Joe
WARNING: multiple messages have this Message-ID (diff)
From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: sasha.levin@oracle.com,
Luis Henriques <luis.henriques@canonical.com>,
Greg KH <gregkh@linuxfoundation.org>
Cc: KY Srinivasan <kys@microsoft.com>,
longli@microsoft.com, JBottomley@Odin.com, alexng@microsoft.com,
Haiyang Zhang <haiyangz@microsoft.com>,
devel@linuxdriverproject.org, linux-scsi@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH][v3.18.y][3.19.y-ckt][4.0.y] storvsc: Set the SRB flags correctly when no data transfer is, needed
Date: Fri, 05 Jun 2015 13:59:24 -0400 [thread overview]
Message-ID: <5571E37C.1070900@canonical.com> (raw)
In-Reply-To: <5571E19C.9000202@canonical.com>
On 06/05/2015 01:51 PM, Joseph Salisbury wrote:
> Hello,
>
> Please consider including mainline commit
> dc45708ca9988656d706940df5fd102672c5de92 in the next v3.18.y, v4.0.y and
> 3.19.y-ckt stable releases. It was
> included in the mainline tree as of v4.1-rc5. It has been tested and
> confirmed to resolve the following bug:
> http://bugs.launchpad.net/bugs/1439780
>
> commit dc45708ca9988656d706940df5fd102672c5de92
> Author: K. Y. Srinivasan <kys@microsoft.com>
> Date: Fri May 1 11:03:02 2015 -0700
>
> storvsc: Set the SRB flags correctly when no data transfer is needed
>
>
>
> Sincerely,
>
> Joseph Salisbury
>
>
It looks like this commit was already cc'd to stable. Sorry for the noise.
Thanks,
Joe
next prev parent reply other threads:[~2015-06-05 17:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 17:51 [PATCH][v3.18.y][3.19.y-ckt][4.0.y] storvsc: Set the SRB flags correctly when no data transfer is, needed Joseph Salisbury
2015-06-05 17:59 ` Joseph Salisbury [this message]
2015-06-05 17:59 ` Joseph Salisbury
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=5571E37C.1070900@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=JBottomley@Odin.com \
--cc=alexng@microsoft.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=luis.henriques@canonical.com \
--cc=sasha.levin@oracle.com \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.