From: Greg KH <greg@kroah.com>
To: Andy Grover <agrover@redhat.com>
Cc: stable@vger.kernel.org,
Christophe Vu-Brugier <cvubrugier@fastmail.fm>,
Leeman Strout <me@enlj.com>,
target-devel <target-devel@vger.kernel.org>
Subject: Re: LIO in 4.2.[12] broken?
Date: Sat, 17 Oct 2015 16:47:05 -0700 [thread overview]
Message-ID: <20151017234705.GE9038@kroah.com> (raw)
In-Reply-To: <560EC681.8010406@redhat.com>
On Fri, Oct 02, 2015 at 11:01:37AM -0700, Andy Grover wrote:
> Hi stable,
>
> Please apply
>
> iscsi-target: Avoid OFMarker + IFMarker negotiation
>
> 673681cafa
>
> to 4.2-stable. It's upstream for 4.3, tested, and people are starting to use
> 4.2 and hit this issue.
Now applied, thanks.
greg k-h
prev parent reply other threads:[~2015-10-17 23:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <560DE782.4040307@mooluv.com>
[not found] ` <20151002193630.6c42ebcc@trantor>
2015-10-02 18:01 ` LIO in 4.2.[12] broken? Andy Grover
2015-10-17 23:47 ` Greg KH [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=20151017234705.GE9038@kroah.com \
--to=greg@kroah.com \
--cc=agrover@redhat.com \
--cc=cvubrugier@fastmail.fm \
--cc=me@enlj.com \
--cc=stable@vger.kernel.org \
--cc=target-devel@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 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).