* STABLE: please pick e4b3448b and f596c884 (nvdimm issues)
@ 2019-03-18 15:54 Adam Borowski
2019-03-18 16:03 ` Greg Kroah-Hartman
0 siblings, 1 reply; 3+ messages in thread
From: Adam Borowski @ 2019-03-18 15:54 UTC (permalink / raw)
To: Greg Kroah-Hartman, stable
Hi Greg!
It seems that somehow two patches apparently dropped through the cracks;
could you please pick them? If you merely stashed them for later then sorry
for noise.
Both are for 4.20 (EOL) and 5.0 only.
e4b3448b dax: Flush partial PMDs correctly
f596c884 nfit: Fix nfit_intel_shutdown_status() command submission
The first is a regression -- a crasher that triggers often during regular
use. The second never worked right, but is relied upon by released software
that would prefer to be notified that the data needs recovery.
ᛗᛖᛟᚹ!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Did ya know that typing "test -j8" instead of "ctest -j8"
⢿⡄⠘⠷⠚⠋⠀ will make your testsuite pass much faster, and fix bugs?
⠈⠳⣄⠀⠀⠀⠀
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: STABLE: please pick e4b3448b and f596c884 (nvdimm issues)
2019-03-18 15:54 STABLE: please pick e4b3448b and f596c884 (nvdimm issues) Adam Borowski
@ 2019-03-18 16:03 ` Greg Kroah-Hartman
2019-03-20 15:39 ` Greg Kroah-Hartman
0 siblings, 1 reply; 3+ messages in thread
From: Greg Kroah-Hartman @ 2019-03-18 16:03 UTC (permalink / raw)
To: Adam Borowski; +Cc: stable
On Mon, Mar 18, 2019 at 04:54:39PM +0100, Adam Borowski wrote:
> Hi Greg!
> It seems that somehow two patches apparently dropped through the cracks;
> could you please pick them? If you merely stashed them for later then sorry
> for noise.
They are still "stashed" for later kernels, along with over 250 patches
still marked for stable inclusion. I'll get to them all over the next
weeks or so.
> Both are for 4.20 (EOL) and 5.0 only.
4.20 is now EOL after this release, no need for anyone to be using that
kernel anymore :)
> e4b3448b dax: Flush partial PMDs correctly
> f596c884 nfit: Fix nfit_intel_shutdown_status() command submission
>
> The first is a regression -- a crasher that triggers often during regular
> use. The second never worked right, but is relied upon by released software
> that would prefer to be notified that the data needs recovery.
Looks good, they will get merged soon.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: STABLE: please pick e4b3448b and f596c884 (nvdimm issues)
2019-03-18 16:03 ` Greg Kroah-Hartman
@ 2019-03-20 15:39 ` Greg Kroah-Hartman
0 siblings, 0 replies; 3+ messages in thread
From: Greg Kroah-Hartman @ 2019-03-20 15:39 UTC (permalink / raw)
To: Adam Borowski; +Cc: stable
On Mon, Mar 18, 2019 at 05:03:21PM +0100, Greg Kroah-Hartman wrote:
> On Mon, Mar 18, 2019 at 04:54:39PM +0100, Adam Borowski wrote:
> > Hi Greg!
> > It seems that somehow two patches apparently dropped through the cracks;
> > could you please pick them? If you merely stashed them for later then sorry
> > for noise.
>
> They are still "stashed" for later kernels, along with over 250 patches
> still marked for stable inclusion. I'll get to them all over the next
> weeks or so.
>
> > Both are for 4.20 (EOL) and 5.0 only.
>
> 4.20 is now EOL after this release, no need for anyone to be using that
> kernel anymore :)
>
> > e4b3448b dax: Flush partial PMDs correctly
> > f596c884 nfit: Fix nfit_intel_shutdown_status() command submission
> >
> > The first is a regression -- a crasher that triggers often during regular
> > use. The second never worked right, but is relied upon by released software
> > that would prefer to be notified that the data needs recovery.
>
> Looks good, they will get merged soon.
All now queued up, thanks.
greg k-h
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-03-20 15:39 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-03-18 15:54 STABLE: please pick e4b3448b and f596c884 (nvdimm issues) Adam Borowski
2019-03-18 16:03 ` Greg Kroah-Hartman
2019-03-20 15:39 ` Greg Kroah-Hartman
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).