From: Richard Weinberger <richard@nod.at>
To: Sohil Mehta <sohil.mehta@intel.com>
Cc: bp <bp@alien8.de>, dave hansen <dave.hansen@linux.intel.com>,
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 v3 0/3] x86: Fix a F00F bug warning and cleanup surrounding code
Date: Wed, 27 May 2026 20:54:34 +0200 (CEST) [thread overview]
Message-ID: <1853680315.28414.1779908074808.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <1507cb8a-a1db-4433-ad5e-0003f192cc33@intel.com>
----- Ursprüngliche Mail -----
> Von: "Sohil Mehta" <sohil.mehta@intel.com>
> (I pressed send too soon)
>
> On 5/27/2026 11:49 AM, Sohil Mehta wrote:
>> On 5/27/2026 11:06 AM, Borislav Petkov wrote:
>>
>>> Why would you even want to backport this to stable? Which of the stable rules
>>> apply here and why are we making too much noise again about obsolete hw?
>>>
>>
>> That's completely fine with me. My primary goal with this posting is to
>> simplify that section of code.
>
> I'll combine the patches into a single one and remove the fixes tag.
Thanks for taking care of it!
prev parent reply other threads:[~2026-05-27 18:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 22:17 [PATCH v3 0/3] x86: Fix a F00F bug warning and cleanup surrounding code 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 ` [PATCH v3 0/3] x86: Fix a F00F bug warning and cleanup surrounding code Borislav Petkov
2026-05-27 6:44 ` 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 [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=1853680315.28414.1779908074808.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.