From: Peter Zijlstra <peterz@infradead.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"Hansen, Dave" <dave.hansen@intel.com>,
Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH -v2 0/5] Further sanitize INTEL_FAM6 naming
Date: Tue, 27 Aug 2019 23:51:35 +0200 [thread overview]
Message-ID: <20190827215135.GI2332@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F7F43EC93@ORSMSX115.amr.corp.intel.com>
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@intel.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.
next prev parent reply other threads:[~2019-08-27 21:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 19:48 [PATCH -v2 0/5] Further sanitize INTEL_FAM6 naming Peter Zijlstra
2019-08-27 19:48 ` [PATCH -v2 1/5] x86/intel: Aggregate big core client naming Peter Zijlstra
2019-08-28 13:03 ` [tip: x86/cpu] " tip-bot2 for Peter Zijlstra
2019-08-27 19:48 ` [PATCH -v2 2/5] x86/intel: Aggregate big core mobile naming Peter Zijlstra
2019-08-28 13:03 ` [tip: x86/cpu] " tip-bot2 for Peter Zijlstra
2019-08-27 19:48 ` [PATCH -v2 3/5] x86/intel: Aggregate big core graphics naming Peter Zijlstra
2019-08-28 13:03 ` [tip: x86/cpu] " tip-bot2 for Peter Zijlstra
2019-08-27 19:48 ` [PATCH -v2 4/5] x86/intel: Aggregate microserver naming Peter Zijlstra
2019-08-28 13:03 ` [tip: x86/cpu] " tip-bot2 for Peter Zijlstra
2019-08-27 19:48 ` [PATCH -v2 5/5] x86/intel: Add common OPTDIFFs Peter Zijlstra
2019-08-28 13:03 ` [tip: x86/cpu] " tip-bot2 for Peter Zijlstra
2019-08-27 20:44 ` [PATCH -v2 0/5] Further sanitize INTEL_FAM6 naming Luck, Tony
2019-08-27 21:51 ` Peter Zijlstra [this message]
2019-08-28 9:33 ` Peter Zijlstra
2019-08-28 12:59 ` Peter Zijlstra
2019-08-28 15:03 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190827215135.GI2332@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).