Re: [PATCH 4.19 000/170] 4.19.14-stable review

[Greg Kroah-Hartman]

On Thu, Jan 10, 2019 at 07:40:39AM -0800, Guenter Roeck wrote:
> On Thu, Jan 10, 2019 at 04:15:40PM +0100, Christoph Biedl wrote:
> > Christoph Biedl wrote...
> > 
> > > Sorry for not getting back to you earlier. Building yesterday's
> > > release (v4.19.14) *failed*, bisect led to
> > >
> > > | commit a9935a12768851762089fda8e5a9daaf0231808e (HEAD)
> > > | Author: Breno Leitao <leitao@xxxxxxxxxx>
> > > | Date:   Mon Nov 26 18:12:00 2018 -0200
> > > |
> > > |     powerpc/tm: Unset MSR[TS] if not recheckpointing
> > >
> > > Reverting that commit seems to be sufficient, build passes then.
> > >
> > > Additionally, neither 4.20 nor 5.0-rc1 show this problem. The
> > > | commit 6f5b9f018f4c7686fd944d920209d1382d320e4e upstream.
> > > builds as well, so I'll try to find the missing prerequisite next.
> > 
> > Cherry-picking
> > 
> > | commit 5c784c8414fba11b62e12439f11e109fb5751f38
> > | Author: Breno Leitao <leitao@xxxxxxxxxx>
> > | Date:   Thu Aug 16 14:21:07 2018 -0300
> > |
> > |     powerpc/tm: Remove msr_tm_active()
> > 
> > makes the build pass. Bruno, does this make sense?
> > 
> As I had reported and suggested well before the release.
> According to Greg those responsible for the patch series rejected that.

Ok, Breno and Christoph, what should I do here?  Should I drop this
patch in the tree or add this new one?  Ideally I can fix this soon as I
don't like having broken trees out there...

thanks,

greg k-h