From: Christoph Hellwig <hch@infradead.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Mike Christie <michaelc@cs.wisc.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Sagi Grimberg <sagig@mellanox.com>,
Nicholas Bellinger <nab@linux-iscsi.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 3.15 099/139] libiscsi, iser: Adjust data_length to include protection information
Date: Wed, 2 Jul 2014 23:05:06 -0700 [thread overview]
Message-ID: <20140703060506.GA17456@infradead.org> (raw)
In-Reply-To: <1404341317.1862.71.camel@ul30vt.home>
On Wed, Jul 02, 2014 at 04:48:37PM -0600, Alex Williamson wrote:
> Thanks for the pointer. It's curious why there was no objection to this
> going into stable if it's been known to be broken for a week.
I've never seen the stable patch on linux-scsi. IMHO it should never
have been proposed for -stable with all the issues it caused.
next prev parent reply other threads:[~2014-07-03 6:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140628174605.352098823@linuxfoundation.org>
[not found] ` <20140628174609.930049472@linuxfoundation.org>
[not found] ` <1404339330.1862.69.camel@ul30vt.home>
2014-07-02 22:44 ` [PATCH 3.15 099/139] libiscsi, iser: Adjust data_length to include protection information Mike Christie
2014-07-02 22:48 ` Alex Williamson
2014-07-03 6:05 ` Christoph Hellwig [this message]
2014-07-02 22:52 ` James Bottomley
2014-07-02 23:19 ` Alex Williamson
2014-07-03 0:05 ` Nicholas A. Bellinger
2014-07-03 6:05 ` Christoph Hellwig
2014-07-03 13:54 ` James Bottomley
2014-07-03 16:27 ` Greg Kroah-Hartman
2014-07-03 16:33 ` Christoph Hellwig
2014-07-03 18:00 ` James Bottomley
2014-07-06 12:27 ` Sagi Grimberg
2014-07-03 16:28 ` Christoph Hellwig
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=20140703060506.GA17456@infradead.org \
--to=hch@infradead.org \
--cc=alex.williamson@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=nab@linux-iscsi.org \
--cc=sagig@mellanox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox