From: Sohil Mehta <sohil.mehta@intel.com>
To: Richard Weinberger <richard@nod.at>, <x86@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <tglx@kernel.org>,
<mingo@redhat.com>, <bp@alien8.de>, <dave.hansen@linux.intel.com>,
<hpa@zytor.com>
Subject: Re: [PATCH 2/2] [RFC] x86: Remove clear_cpu_bug()
Date: Thu, 19 Feb 2026 17:30:00 -0800 [thread overview]
Message-ID: <dc03b6e6-1a32-47e7-ba00-6ae6de6d39c6@intel.com> (raw)
In-Reply-To: <20260216104343.3625292-2-richard@nod.at>
On 2/16/2026 2:43 AM, Richard Weinberger wrote:
> F00F was the only user of clear_cpu_bug().
> With no users left, remove this helper.
>
Yeah, this function isn't used commonly. The 2nd last user was removed
~9 years back.
> Signed-off-by: Richard Weinberger <richard@nod.at>
> ---
> arch/x86/include/asm/cpufeature.h | 1 -
> 1 file changed, 1 deletion(-)
>
Reviewed-by: Sohil Mehta <sohil.mehta@intel.com>
> diff --git a/arch/x86/include/asm/cpufeature.h b/arch/x86/include/asm/cpufeature.h
> index 3ddc1d33399b..90680f978d43 100644
> --- a/arch/x86/include/asm/cpufeature.h
> +++ b/arch/x86/include/asm/cpufeature.h
> @@ -125,7 +125,6 @@ static __always_inline bool _static_cpu_has(u16 bit)
>
> #define cpu_has_bug(c, bit) cpu_has(c, (bit))
> #define set_cpu_bug(c, bit) set_cpu_cap(c, (bit))
> -#define clear_cpu_bug(c, bit) clear_cpu_cap(c, (bit))
>
> #define static_cpu_has_bug(bit) static_cpu_has((bit))
> #define boot_cpu_has_bug(bit) cpu_has_bug(&boot_cpu_data, (bit))
next prev parent reply other threads:[~2026-02-20 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 10:43 [PATCH 1/2] x86: Don't clear X86_BUG_F00F before setting it Richard Weinberger
2026-02-16 10:43 ` [PATCH 2/2] [RFC] x86: Remove clear_cpu_bug() Richard Weinberger
2026-02-20 1:30 ` Sohil Mehta [this message]
2026-02-20 1:25 ` [PATCH 1/2] x86: Don't clear X86_BUG_F00F before setting it Sohil Mehta
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=dc03b6e6-1a32-47e7-ba00-6ae6de6d39c6@intel.com \
--to=sohil.mehta@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=richard@nod.at \
--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®