On Thu, Sep 20, 2018 at 4:00 PM Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote: > > On Thu, 20 Sep 2018, Evan Green wrote: > > On Thu, Aug 30, 2018 at 7:29 AM Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote: > > > > > > On Thu, 30 Aug 2018, John Crispin wrote: > > > > > > > > Sry, that disturbing you all, but what are the conclusion here for 4.14.y? > > > > > - take Thomas's patch https://lore.kernel.org/patchwork/patch/969521/#1162900 > > > > > - revert commit 2d898915ccf4838c04531c51a598469e921a5eb5 > > > > > > > > Hi Frederic, > > > > > > > > I reported this very issue to tglx last night and he asked me to verify his > > > > proposed patch which i just did. I can confirm the the patch fixes the issue > > > > on 4.14.67 and Greg should add it to the stable queue please. > > > > > > > > Tested-by: John Crispin <john@xxxxxxxxxxx> > > > > > > Let me whip up a proper patch with changelog. > > > > > Hi Thomas, > > Did this patch ever go anywhere? I believe it fixes the prints I'm > > seeing in our kernel, and I wondered if the official patch was > > somewhere. > > It's out there: > > https://lore.kernel.org/patchwork/patch/979451/ > > I assume that it has fallen through the stable cracks. > Thank you! I hope it gets pulled in. -Evan
