mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 1/3] x86/mce: Add CPU_SUP_* dependencies for Intel/Zhaoxin MCE features
Date: Wed, 11 Nov 2026 07:46:32 -0800	[thread overview]
Message-ID: <a7555a3a-10f1-4066-93fc-a5c60f8deea8@intel.com> (raw)
In-Reply-To: <20261031-processor_select_is_not_an_expert_feature-v1-1-6227bdbbe5a9@kernel.org>

On 10/31/26 00:51, Vincent Mailhol wrote:
>  config X86_MCE_INTEL
>  	def_bool y
>  	prompt "Intel MCE features"
> -	depends on X86_MCE && X86_LOCAL_APIC
> +	depends on X86_MCE && X86_LOCAL_APIC && (CPU_SUP_INTEL || CPU_SUP_ZHAOXIN)

Is this to help end users? If so, it seems like it might also be nice to
improve the only human-visible part of this: the prompt text.

  reply	other threads:[~2026-11-11 15:46 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 [this message]
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
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=a7555a3a-10f1-4066-93fc-a5c60f8deea8@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®