From: Sohil Mehta <sohil.mehta@intel.com>
To: Tony Luck <tony.luck@intel.com>, <x86@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
<linux-kernel@vger.kernel.org>, <patches@lists.linux.dev>
Subject: Re: [PATCH] x86/cpu: Rename and move CPU model entry for Diamond Rapids
Date: Mon, 11 Aug 2025 16:58:36 -0700 [thread overview]
Message-ID: <956ba4ef-1ebb-4466-a584-5b06076bcf81@intel.com> (raw)
In-Reply-To: <20250811213345.7029-1-tony.luck@intel.com>
On 8/11/2025 2:33 PM, Tony Luck wrote:
...
> PeterZ agreed and posted a patch[1] to fix the name and move it in
> sequence with other Xeon servers. But without a commit description or
> sign-off the patch wasn't ever applied.
>
> Patch updated to cover one additional use of the #define by turbostat
> and to
Some of this patch handling information doesn't seem relevant to the
commit message. It can probably go below the --- line or skipped while
applying the patch.
...
>
> Originally-by: Peter Zijlstra <peterz@infradead.org>
> Signed-off-by: Tony Luck <tony.luck@intel.com>
> ---
Reviewed-by: Sohil Mehta <sohil.mehta@intel.com>
prev parent reply other threads:[~2025-08-11 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 21:33 Tony Luck
2025-08-11 23:58 ` Sohil Mehta [this message]
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=956ba4ef-1ebb-4466-a584-5b06076bcf81@intel.com \
--to=sohil.mehta@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®