From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: stable@vger.kernel.org
Subject: Can you hold off on 1e793f6fc0db920400574211c48f9157a37e3945
Date: Sat, 12 Nov 2016 09:22:04 -0800 [thread overview]
Message-ID: <1478971324.3290.10.camel@HansenPartnership.com> (raw)
The patch
commit 1e793f6fc0db920400574211c48f9157a37e3945
Author: Kashyap Desai <kashyap.desai@broadcom.com>
Date: Fri Oct 21 06:33:32 2016 -0700
scsi: megaraid_sas: Fix data integrity failure for JBOD
(passthrough) devices
Is fatally flawed. There's another backported fix for it coming:
commit 5e5ec1759dd663a1d5a2f10930224dd009e500e8
Author: Sumit Saxena <sumit.saxena@broadcom.com>
Date: Wed Nov 9 02:59:42 2016 -0800
scsi: megaraid_sas: fix macro MEGASAS_IS_LOGICAL to avoid
regression
It's in a pull request now, but when it hits, could you apply both
together to stable to avoid any stable regression issues?
Thanks,
James
next reply other threads:[~2016-11-12 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-12 17:22 James Bottomley [this message]
2016-11-14 7:38 ` Can you hold off on 1e793f6fc0db920400574211c48f9157a37e3945 Greg KH
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=1478971324.3290.10.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.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;
as well as URLs for NNTP newsgroup(s).