mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Sohil Mehta <sohil.mehta@intel.com>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, Thomas Gleixner <tglx@kernel.org>,
	Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	Richard Weinberger <richard@nod.at>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Tony Luck <tony.luck@intel.com>,
	"Ahmed S . Darwish" <darwi@linutronix.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] x86: Fix a F00F bug warning and cleanup surrounding code
Date: Sun, 24 May 2026 09:33:55 -0700	[thread overview]
Message-ID: <20260524163355.GAahMocxUTCLstCTrs@fat_crate.local> (raw)
In-Reply-To: <20260518221718.3303288-1-sohil.mehta@intel.com>

On Mon, May 18, 2026 at 03:17:15PM -0700, Sohil Mehta wrote:
> Changes in v3:
>  - Remove the notice announcing the F00F bug workaround instead of
>    simplifying it.
>  - Pick up review tags from Ahmed.
> 
> v2: https://lore.kernel.org/all/20260515002500.2463393-1-sohil.mehta@intel.com/
> 
> Summary:
> The series fixes a harmless "alternatives_patched" warning that affects
> the original Pentium (Family 5) processors with SMP. It also removes the
> kernel announcement that the F00F bug workaround is in place. Mainly,
> the patches simplify and reduce lines of code.
> 
> Original v1 post by Richard Weinberger:
> https://lore.kernel.org/lkml/20260216104343.3625292-1-richard@nod.at/
> 
> The Fixes tag in patch 1 isn't strictly 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: Remove the F00F bug workaround notice
> 
>  arch/x86/include/asm/cpufeature.h |  1 -
>  arch/x86/kernel/cpu/intel.c       | 15 +++------------
>  2 files changed, 3 insertions(+), 13 deletions(-)

Why are there three patches doing one logical thing?

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  parent reply	other threads:[~2026-05-24 16:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18 22:17 Sohil Mehta
2026-05-18 22:17 ` [PATCH v3 1/3] x86/cpu/intel: Don't clear X86_BUG_F00F before setting it Sohil Mehta
2026-05-18 22:17 ` [PATCH v3 2/3] x86/cpu/intel: Remove the F00F bug workaround notice Sohil Mehta
2026-05-19  9:00   ` Ahmed S. Darwish
2026-05-18 22:17 ` [PATCH v3 3/3] x86/cpufeature: Remove clear_cpu_bug() Sohil Mehta
2026-05-24 16:33 ` Borislav Petkov [this message]
2026-05-27  6:44   ` [PATCH v3 0/3] x86: Fix a F00F bug warning and cleanup surrounding code Sohil Mehta
2026-05-27 18:06     ` Borislav Petkov
2026-05-27 18:49       ` Sohil Mehta
2026-05-27 18:51         ` Sohil Mehta
2026-05-27 18:54           ` Richard Weinberger

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=20260524163355.GAahMocxUTCLstCTrs@fat_crate.local \
    --to=bp@alien8.de \
    --cc=andrew.cooper3@citrix.com \
    --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=richard@nod.at \
    --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 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®