From: "Ahmed S. Darwish" <darwi@linutronix.de>
To: Sohil Mehta <sohil.mehta@intel.com>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
Borislav Petkov <bp@alien8.de>,
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>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] x86/cpu/intel: Remove the F00F bug workaround notice
Date: Tue, 19 May 2026 11:00:30 +0200 [thread overview]
Message-ID: <agwmrha1xd-rekHT@lx-t490> (raw)
In-Reply-To: <20260518221718.3303288-3-sohil.mehta@intel.com>
On Mon, 18 May 2026, Sohil Mehta wrote:
>
> The F00F bug workaround announcement goes through a lot of effort to
> print the kernel notice exactly once. CPU bugs with workarounds
> typically don't require user notifications. If needed, the presence of
> the F00F bug can be determined through /proc/cpuinfo.
>
> Remove the notice and the surrounding logic to print it once.
>
> Signed-off-by: Sohil Mehta <sohil.mehta@intel.com>
> ---
Thanks for removing it.
Reviewed-by: Ahmed S. Darwish <darwi@linutronix.de>
next prev parent reply other threads:[~2026-05-19 9:00 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 [this message]
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
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=agwmrha1xd-rekHT@lx-t490 \
--to=darwi@linutronix.de \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.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 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.