diff for duplicates of <1502210041.7877.5.camel@gmx.de> diff --git a/a/1.txt b/N1/1.txt index 02fd346..f098d45 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,36 +1,30 @@ On Tue, 2017-08-08 at 09:22 -0700, Greg KH wrote: > On Sun, Jul 30, 2017 at 03:50:15PM +0200, Oleksandr Natalenko wrote: > > Hello Mike et al. -> >=20 -> > On ned=C4=9Ble 30. =C4=8Dervence 2017 7:12:31 CEST Mike Galbraith wrote= -: +> > +> > On neděle 30. července 2017 7:12:31 CEST Mike Galbraith wrote: > > > FWIW, first thing I'd do is update that 4.12.0 to 4.12.4, and see if > > > stable fixed it. -> >=20 +> > > > My build already includes v4.12.4. -> >=20 +> > > > > If not, I'd find these two commits irresistible. -> > >=20 -> > > 5f042e7cbd9eb blk-mq: Include all present CPUs in the default queue m= -apping +> > > +> > > 5f042e7cbd9eb blk-mq: Include all present CPUs in the default queue mapping > > > 4b855ad37194f blk-mq: Create hctx for each present CPU -> >=20 -> > I've applied these 2 commits, and cannot reproduce the issue anymore. L= -ooks=20 +> > +> > I've applied these 2 commits, and cannot reproduce the issue anymore. Looks > > like a perfect hit, thanks! -> >=20 -> > > 'course applying random upstream bits does come with some risk, tryin= -g -> > > a kernel already containing them has less "entertainment" potential.= -=20 -> >=20 -> > Should you consider applying them to v4.12.x stable series? CC'ing Greg= - just=20 +> > +> > > 'course applying random upstream bits does come with some risk, trying +> > > a kernel already containing them has less "entertainment" potential. +> > +> > Should you consider applying them to v4.12.x stable series? CC'ing Greg just > > in case. ->=20 +> > I can queue these up if I get an ack from the developers/maintainers > that it is ok to do so... ->=20 +> > {hint} {hint++} diff --git a/a/content_digest b/N1/content_digest index 259493a..9b2be66 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -16,36 +16,30 @@ "On Tue, 2017-08-08 at 09:22 -0700, Greg KH wrote:\n" "> On Sun, Jul 30, 2017 at 03:50:15PM +0200, Oleksandr Natalenko wrote:\n" "> > Hello Mike et al.\n" - "> >=20\n" - "> > On ned=C4=9Ble 30. =C4=8Dervence 2017 7:12:31 CEST Mike Galbraith wrote=\n" - ":\n" + "> > \n" + "> > On ned\304\233le 30. \304\215ervence 2017 7:12:31 CEST Mike Galbraith wrote:\n" "> > > FWIW, first thing I'd do is update that 4.12.0 to 4.12.4, and see if\n" "> > > stable fixed it.\n" - "> >=20\n" + "> > \n" "> > My build already includes v4.12.4.\n" - "> >=20\n" + "> > \n" "> > > If not, I'd find these two commits irresistible.\n" - "> > >=20\n" - "> > > 5f042e7cbd9eb blk-mq: Include all present CPUs in the default queue m=\n" - "apping\n" + "> > > \n" + "> > > 5f042e7cbd9eb blk-mq: Include all present CPUs in the default queue mapping\n" "> > > 4b855ad37194f blk-mq: Create hctx for each present CPU\n" - "> >=20\n" - "> > I've applied these 2 commits, and cannot reproduce the issue anymore. L=\n" - "ooks=20\n" + "> > \n" + "> > I've applied these 2 commits, and cannot reproduce the issue anymore. Looks \n" "> > like a perfect hit, thanks!\n" - "> >=20\n" - "> > > 'course applying random upstream bits does come with some risk, tryin=\n" - "g\n" - "> > > a kernel already containing them has less \"entertainment\" potential.=\n" - "=20\n" - "> >=20\n" - "> > Should you consider applying them to v4.12.x stable series? CC'ing Greg=\n" - " just=20\n" + "> > \n" + "> > > 'course applying random upstream bits does come with some risk, trying\n" + "> > > a kernel already containing them has less \"entertainment\" potential. \n" + "> > \n" + "> > Should you consider applying them to v4.12.x stable series? CC'ing Greg just \n" "> > in case.\n" - ">=20\n" + "> \n" "> I can queue these up if I get an ack from the developers/maintainers\n" "> that it is ok to do so...\n" - ">=20\n" + "> \n" "> {hint}\n" "\n" "{hint++}\n" @@ -56,4 +50,4 @@ "\n" "\t-Mike" -671b3dffd0b83f76d90ebd8f479efb71ac047c3ace5b15917e4142e8004a0e20 +506a47dbdd7ff28bb0e72ff583224ef1153f3465f60d995c4c90e7cd8fd8580a
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.