From: Richard Weinberger <richard@nod.at>
To: Sohil Mehta <sohil.mehta@intel.com>
Cc: dave hansen <dave.hansen@linux.intel.com>, bp <bp@alien8.de>,
x86 <x86@kernel.org>, Thomas Gleixner <tglx@kernel.org>,
mingo <mingo@redhat.com>, hpa <hpa@zytor.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
andrew cooper3 <andrew.cooper3@citrix.com>,
Tony Luck <tony.luck@intel.com>,
"Ahmed S. Darwish" <darwi@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] x86: Fix a F00F bug warning and cleanup surrounding code
Date: Fri, 15 May 2026 08:18:15 +0200 (CEST) [thread overview]
Message-ID: <1502416086.3154.1778825895775.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <20260515002500.2463393-1-sohil.mehta@intel.com>
----- Ursprüngliche Mail -----
> Von: "Sohil Mehta" <sohil.mehta@intel.com>
> This is an iteration of the series posted earlier by Richard Weinberger.
> https://lore.kernel.org/lkml/20260216104343.3625292-1-richard@nod.at/
>
> The patches primarily fix a harmless "alternatives_patched" warning that
> affects the original Pentium (Family 5) processors with SMP. In this
> revision, I reworded the commit messages and added a patch to simplify
> the warning logic for the F00F bug. The patches seemed worth reposting
> because the scope of the change is limited and it reduces lines of code.
>
> The series is split into three patches for easier review. Let me know if
> it would be preferable to merge them. Also, I wasn't sure whether the Fixes
> tag in patch 1 is necessary. I left it inplace as Richard had it in his
> original series, but it can be removed to avoid backporting hassles.
>
> Richard Weinberger (2):
> x86/cpu/intel: Don't clear X86_BUG_F00F before setting it
> x86/cpufeature: Remove clear_cpu_bug()
>
> Sohil Mehta (1):
> x86/cpu/intel: Simplify F00F bug notice using pr_notice_once()
Thanks for reviving these patches!
//richard
prev parent reply other threads:[~2026-05-15 6:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 0:24 [PATCH v2 0/3] x86: Fix a F00F bug warning and cleanup surrounding code Sohil Mehta
2026-05-15 0:24 ` [PATCH v2 1/3] x86/cpu/intel: Don't clear X86_BUG_F00F before setting it Sohil Mehta
2026-05-15 0:24 ` [PATCH v2 2/3] x86/cpu/intel: Simplify F00F bug notice using pr_notice_once() Sohil Mehta
2026-05-15 0:25 ` [PATCH v2 3/3] x86/cpufeature: Remove clear_cpu_bug() Sohil Mehta
2026-05-15 6:18 ` Richard Weinberger [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=1502416086.3154.1778825895775.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=darwi@linutronix.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sohil.mehta@intel.com \
--cc=tglx@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.