From: Greg KH <gregkh@linuxfoundation.org>
To: Kashyap Desai <kashyap.desai@broadcom.com>
Cc: Sumit Saxena <sumit.saxena@broadcom.com>,
emilne@redhat.com, hare@suse.com, martin.petersen@oracle.com,
thenzl@redhat.com, stable@vger.kernel.org,
stable-commits@vger.kernel.org
Subject: Re: Patch "scsi: megaraid_sas: Fix data integrity failure for JBOD (passthrough) devices" has been added to the 4.8-stable tree
Date: Wed, 9 Nov 2016 11:08:13 +0100 [thread overview]
Message-ID: <20161109100813.GA27827@kroah.com> (raw)
In-Reply-To: <fe425e4e97d881ac19f44f90cb3cd3d5@mail.gmail.com>
On Wed, Nov 09, 2016 at 02:45:30PM +0530, Kashyap Desai wrote:
> > >> please let
> > > >> ><stable@vger.kernel.org> know about it.
> > > >>
> > > >> There will be follow up patch which I will be sending in sometime
> > > >> so follow patch needs to be applied along with this patch.
> > > >
> > > >Does that mean that this patch on its own is broken?
> > > >
> > > >confused,
> > > Yes this patch is broken and follow up patch will fix that. I am doing
> > > some testing with fix and will send it in sometime.
> >
> > So should I drop this one from the stable trees until that one is
> merged?
>
> Greg - We are sending another patch which is small fix on top of this one.
> It is critical regression.
> Not sure which will be a good .. To reject or hold current patch. Current
> patch is definitely a not good to keep without upcoming fix.
>
> To avoid confusion, let's reject this patch and apply once full fix is
> available (by EOD).
Ok, I've dropped this from the stable queue, please let me know when the
"fix" is in Linus's tree, so I can re-add this patch, and the fix patch
(please let me know what the git ids are for both.)
thanks,
greg k-h
next prev parent reply other threads:[~2016-11-09 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 8:18 Patch "scsi: megaraid_sas: Fix data integrity failure for JBOD (passthrough) devices" has been added to the 4.8-stable tree gregkh
[not found] ` <a48ab14b1e168f2bee2fcc75f3f440ff@mail.gmail.com>
2016-11-09 8:49 ` Greg KH
[not found] ` <8cf3887e20e37314f49066cea65369ee@mail.gmail.com>
2016-11-09 9:03 ` Greg KH
[not found] ` <fe425e4e97d881ac19f44f90cb3cd3d5@mail.gmail.com>
2016-11-09 10:08 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-14 7:41 gregkh
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=20161109100813.GA27827@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=emilne@redhat.com \
--cc=hare@suse.com \
--cc=kashyap.desai@broadcom.com \
--cc=martin.petersen@oracle.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=sumit.saxena@broadcom.com \
--cc=thenzl@redhat.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 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.