[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190827215135.GI2332@hirez.programming.kicks-ass.net>
Date: Tue, 27 Aug 2019 23:51:35 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: "Luck, Tony" <tony.luck@...el.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
"Hansen, Dave" <dave.hansen@...el.com>,
Borislav Petkov <bp@...en8.de>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH -v2 0/5] Further sanitize INTEL_FAM6 naming
On Tue, Aug 27, 2019 at 08:44:23PM +0000, Luck, Tony wrote:
> > I'm reposting because the version Ingo applied and partially fixed up still
> > generates build bot failure.
>
> Looks like this version gets them all. I built my standard config, allmodconfig and allyesconfig.
>
> Reviewed-by: Tony Luck <tony.luck@...el.com>
>
> What happens next? Will Ingo back out the previous set & his partial fixup and replace
> with this series? Or just slap one extra patch on top of what is already in tip?
>
> First option changes a TIP branch
This is uncommon, but not unheard of. I'll talk to Ingo and Thomas
tomorrow to see what would be the best way forward.
Powered by blists - more mailing lists