[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87wo72uv3z.fsf@mpe.ellerman.id.au>
Date: Mon, 30 Mar 2020 19:04:16 +1100
From: Michael Ellerman <mpe@...erman.id.au>
To: Borislav Petkov <bp@...e.de>,
Stephen Rothwell <sfr@...b.auug.org.au>
Cc: "H.J. Lu" <hjl.tools@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kees Cook <keescook@...omium.org>,
PowerPC <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: linux-next: build failure after merge of the tip tree
Borislav Petkov <bp@...e.de> writes:
> On Mon, Mar 30, 2020 at 03:08:19PM +1100, Stephen Rothwell wrote:
>> What you really need is an Ack from the PowerPC people for the fix you
>> suggested and then tha fix should go in the same series that is now
>> causing the failure (preferably before the problematic (for PowerPC)
>> patch.
>
> I'll zap this commit from the tip lineup. There's always another merge
> window.
Or just squash the hunk Stephen posted into the commit, which is what I
thought would happen to begin with.
You can have my ack for it:
Acked-by: Michael Ellerman <mpe@...erman.id.au> (powerpc)
cheers
Powered by blists - more mailing lists