[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190110154039.GA26814@roeck-us.net>
Date: Thu, 10 Jan 2019 07:40:39 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: Christoph Biedl <linux-kernel.bfrz@...chmal.in-ulm.de>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Breno Leitao <leitao@...ian.org>, linux-kernel@...r.kernel.org,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
shuah@...nel.org, patches@...nelci.org,
ben.hutchings@...ethink.co.uk, lkft-triage@...ts.linaro.org,
stable@...r.kernel.org
Subject: Re: [PATCH 4.19 000/170] 4.19.14-stable review
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@...ian.org>
> > | 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@...ian.org>
> | 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.
Guenter
Powered by blists - more mailing lists