From: Dave Hansen <dave.hansen@intel.com>
To: Tony Luck <tony.luck@intel.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org, patches@lists.linux.dev
Subject: Re: [PATCH] x86/cpu: Add/fix core comments for {Panther,Nova} Lake
Date: Tue, 28 Oct 2025 12:57:51 -0700 [thread overview]
Message-ID: <704189df-908d-469a-b719-4d18ce0bcdf2@intel.com> (raw)
In-Reply-To: <20251028172948.6721-1-tony.luck@intel.com>
On 10/28/25 10:29, Tony Luck wrote:
> -#define INTEL_NOVALAKE IFM(18, 0x01)
> -#define INTEL_NOVALAKE_L IFM(18, 0x03)
> +#define INTEL_NOVALAKE IFM(18, 0x01) /* Coyote Cove / Arctic Wolf */
> +#define INTEL_NOVALAKE_L IFM(18, 0x03) /* Coyote Cove / Arctic Wolf */
Is it even worth keeping the core names in there? This is an example
where they're causing churn. If nobody cares, maybe we should just
zap them, or at least stop putting them in there for new CPUs.
next prev parent reply other threads:[~2025-10-28 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 17:29 [PATCH] x86/cpu: Add/fix core comments for {Panther,Nova} Lake Tony Luck
2025-10-28 19:57 ` Dave Hansen [this message]
2025-10-28 20:44 ` Andrew Cooper
2025-10-28 21:19 ` Luck, Tony
2025-10-29 8:42 ` [tip: x86/urgent] " tip-bot2 for Tony Luck
2025-10-30 10:36 ` 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=704189df-908d-469a-b719-4d18ce0bcdf2@intel.com \
--to=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--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