From: alexander.levin@verizon.com
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Randy Dunlap <rdunlap@infradead.org>,
Dashi DS1 Cao <caods1@lenovo.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
stable <stable@vger.kernel.org>
Subject: Re: version 3.18.44 to 3.18.45 introduced a bug in "drivers/scsi/megaraid/megaraid_sas_base.c"
Date: Tue, 13 Dec 2016 20:51:31 +0000 [thread overview]
Message-ID: <20161213205129.w5xzwwuwy5llqywc@sasha-lappy> (raw)
In-Reply-To: <20161213164733.GA21910@kroah.com>
On Tue, Dec 13, 2016 at 08:47:33AM -0800, Greg Kroah-Hartman wrote:
> On Tue, Dec 13, 2016 at 08:43:41AM -0800, James Bottomley wrote:
> > On Tue, 2016-12-13 at 08:33 -0800, Randy Dunlap wrote:
> > > On 12/13/16 08:30, Greg Kroah-Hartman wrote:
> > > > I don't maintain 3.18-stable :)
> > > >
> > > > thanks,
> > > >
> > > > greg k-h
> > > >
> > >
> > > Thanks. My bad.
> > >
> > > adding Sasha.
> >
> > This was all covered here:
> >
> > https://www.spinics.net/lists/stable/msg150608.html
> >
> > How did it get missed, and what should the process be?
>
> I don't know how that got missed, did the "fixup" patch never make it
> into 3.18-stable? I know Sasha has been slow on that kernel, and it's
> about to go end-of-life, so perhaps he's just releasing them on a slower
> cycle at the moment...
I think that what happened there is that I built the branch before the fixup
was upstreamed, so I never noticed that.
It's queued up right now, but I don't think I'll make another release except
a final one in January when it EOLs.
If this fix is urgent for anyone then something is wrong as this kernel dies
in two weeks...
--
Thanks,
Sasha
prev parent reply other threads:[~2016-12-13 20:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 10:56 version 3.18.44 to 3.18.45 introduced a bug in "drivers/scsi/megaraid/megaraid_sas_base.c" Dashi DS1 Cao
2016-12-13 16:08 ` Randy Dunlap
2016-12-13 16:30 ` Greg Kroah-Hartman
2016-12-13 16:33 ` Randy Dunlap
2016-12-13 16:43 ` James Bottomley
2016-12-13 16:47 ` Greg Kroah-Hartman
2016-12-13 20:51 ` alexander.levin [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=20161213205129.w5xzwwuwy5llqywc@sasha-lappy \
--to=alexander.levin@verizon.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=caods1@lenovo.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rdunlap@infradead.org \
--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).