From: Peter Zijlstra <peterz@infradead.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Borislav Petkov <bp@alien8.de>, "x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/cpu: Add new Alderlake and Raptorlake CPU model numbers
Date: Tue, 19 Apr 2022 10:56:03 +0200 [thread overview]
Message-ID: <20220419085603.GO2731@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <YlS7n7Xtso9BXZA2@agluck-desk3.sc.intel.com>
On Mon, Apr 11, 2022 at 04:37:03PM -0700, Luck, Tony wrote:
> Intel is subdividing the mobile segment with additional models
> with the same codename. Using the Intel "N" and "P" suffices
> for these will be less confusing than trying to map to some
> different naming convention.
>
> Signed-off-by: Tony Luck <tony.luck@intel.com>
> ---
>
> I think the earlier patch for Alderlake "N" got stuck in limbo
> trying to resolve whether we should add the "_N" suffix to our list
> of acceptable CPU model #define names. Now we have another one "_P".
>
> Can we just take these, and move on?
Yeah, I suppose so.
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Let's hope our marketing team will stick with these names for a little
while atleast :/
next prev parent reply other threads:[~2022-04-19 8:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 21:56 [PATCH] x86/cpu: Add a third Alderlake CPU model number Tony Luck
2022-03-30 13:43 ` Peter Zijlstra
2022-03-30 19:57 ` Luck, Tony
2022-04-11 23:37 ` [PATCH] x86/cpu: Add new Alderlake and Raptorlake CPU model numbers Luck, Tony
2022-04-19 8:56 ` Peter Zijlstra [this message]
2022-04-19 10:01 ` Borislav Petkov
2022-04-19 10:16 ` [tip: x86/urgent] " tip-bot2 for Tony Luck
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=20220419085603.GO2731@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--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