From: Thomas Gleixner <tglx@kernel.org>
To: Maciej Wieczor-Retman <m.wieczorretman@pm.me>,
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>,
Peter Zijlstra <peterz@infradead.org>
Cc: m.wieczorretman@pm.me,
Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 2/3] x86/cpu: Check if feature string is non-zero
Date: Tue, 24 Feb 2026 21:24:45 +0100 [thread overview]
Message-ID: <87pl5tubxu.ffs@tglx> (raw)
In-Reply-To: <f751f2c87ac3b06db8b28a9eccd3c95f8443b94b.1771936214.git.m.wieczorretman@pm.me>
On Tue, Feb 24 2026 at 12:40, Maciej Wieczor-Retman wrote:
> diff --git a/include/linux/cpu.h b/include/linux/cpu.h
> index 8239cd95a005..acd3f0f4867a 100644
> --- a/include/linux/cpu.h
> +++ b/include/linux/cpu.h
> @@ -233,4 +233,6 @@ int arch_get_indir_br_lp_status(struct task_struct *t, unsigned long __user *sta
> int arch_set_indir_br_lp_status(struct task_struct *t, unsigned long status);
> int arch_lock_indir_br_lp_status(struct task_struct *t, unsigned long status);
>
> +const char *x86_cap_name(unsigned int bit, char *buf);
This x86 specific muck has no place in the generic header file. That's
what architecture specific headers are for.
Thanks,
tglx
next prev parent reply other threads:[~2026-02-24 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 12:38 [PATCH v7 0/3] x86: Capability bits fix and required bits sanity check Maciej Wieczor-Retman
2026-02-24 12:40 ` [PATCH v7 1/3] x86/cpu: Clear feature bits disabled at compile-time Maciej Wieczor-Retman
2026-02-24 12:40 ` [PATCH v7 2/3] x86/cpu: Check if feature string is non-zero Maciej Wieczor-Retman
2026-02-24 20:24 ` Thomas Gleixner [this message]
2026-02-25 7:58 ` Maciej Wieczor-Retman
2026-02-24 12:40 ` [PATCH v7 3/3] x86/cpu: Do a sanity check on required feature bits Maciej Wieczor-Retman
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=87pl5tubxu.ffs@tglx \
--to=tglx@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.wieczorretman@pm.me \
--cc=maciej.wieczor-retman@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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