From: Dave Hansen <dave.hansen@intel.com>
To: Vincent Mailhol <mailhol@kernel.org>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] x86/cpu: don't gate PROCESSOR_SELECT with EXPERT
Date: Wed, 11 Nov 2026 07:45:51 -0800 [thread overview]
Message-ID: <94a39731-050a-4dbf-90fb-1ffccb2f49dc@intel.com> (raw)
In-Reply-To: <30db0b9c-cd43-409e-a39c-f91dee446d55@kernel.org>
On 11/11/26 07:38, Vincent Mailhol wrote:
> Have you had a chance to read my replies?
I did, but I just don't have a lot more to add.
We're honestly moving away from using the CPU_SUP_* options as opposed
to expanding them or making them more usable.
If you want the first two applied, please resend them with an updated
changelog and cover letter.
next prev parent reply other threads:[~2026-11-11 15:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 7:51 [PATCH 0/3] x86: Make processor vendor selection available without EXPERT Vincent Mailhol
2026-10-31 7:51 ` [PATCH 1/3] x86/mce: Add CPU_SUP_* dependencies for Intel/Zhaoxin MCE features Vincent Mailhol
2026-11-11 15:46 ` Dave Hansen
2026-11-11 16:16 ` Vincent Mailhol
2026-10-31 7:51 ` [PATCH 2/3] x86/numa: Add CPU_SUP_AMD dependency for legacy AMD NUMA Vincent Mailhol
2026-10-31 7:51 ` [PATCH 3/3] x86/cpu: don't gate PROCESSOR_SELECT with EXPERT Vincent Mailhol
2026-10-31 13:58 ` Dave Hansen
2026-11-01 11:26 ` Vincent Mailhol
2026-11-11 15:38 ` Vincent Mailhol
2026-11-11 15:45 ` Dave Hansen [this message]
2026-10-31 21:43 ` [PATCH 0/3] x86: Make processor vendor selection available without EXPERT Borislav Petkov
2026-11-01 11:27 ` Vincent Mailhol
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=94a39731-050a-4dbf-90fb-1ffccb2f49dc@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--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®