From: Andrew Cooper <andrew.cooper3@citrix.com>
To: dave.hansen@intel.com
Cc: linux-kernel@vger.kernel.org, patches@lists.linux.dev,
tony.luck@intel.com, x86@kernel.org
Subject: Re: [PATCH] x86/cpu: Add/fix core comments for {Panther,Nova} Lake
Date: Tue, 28 Oct 2025 20:44:31 +0000 [thread overview]
Message-ID: <19c03c72-9fe3-4712-872e-324e65030dc0@citrix.com> (raw)
In-Reply-To: <704189df-908d-469a-b719-4d18ce0bcdf2@intel.com>
> 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.
Personally speaking, I find it very useful to have the cross reference
all in one place.
This file is the most concise source of information I'm aware of.
~Andrew
next prev parent reply other threads:[~2025-10-28 20:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 17:29 Tony Luck
2025-10-28 19:57 ` Dave Hansen
2025-10-28 20:44 ` Andrew Cooper [this message]
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=19c03c72-9fe3-4712-872e-324e65030dc0@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=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
all inboxes | Powered by JetHome®