From: Borislav Petkov <bp@alien8.de>
To: Maciej Wieczor-Retman <m.wieczorretman@pm.me>
Cc: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Farrah Chen <farrah.chen@intel.com>,
Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 1/3] x86/cpu: Clear feature bits disabled at compile-time
Date: Tue, 03 Mar 2026 05:59:39 +0000 [thread overview]
Message-ID: <D5F67944-7C7B-4675-A495-E30CCCD4A606@alien8.de> (raw)
In-Reply-To: <aaX_EBPkvou6POYe@wieczorr-mobl1.localdomain>
On March 2, 2026 9:22:47 PM UTC, Maciej Wieczor-Retman <m.wieczorretman@pm.me> wrote:
>Maybe it could fall under the 'some "oh, that's not good" issue'? :)
More like "no one noticed/complained until now so why are we making waves and generating unnecessary work now" thing...
--
Small device. Typos and formatting crap
next prev parent reply other threads:[~2026-03-03 7:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 15:24 [PATCH v8 0/3] x86: Capability bits fix and required bits sanity check Maciej Wieczor-Retman
2026-03-02 15:25 ` [PATCH v8 1/3] x86/cpu: Clear feature bits disabled at compile-time Maciej Wieczor-Retman
2026-03-02 19:31 ` Borislav Petkov
2026-03-02 19:48 ` Maciej Wieczor-Retman
2026-03-02 20:25 ` Borislav Petkov
2026-03-02 20:38 ` Maciej Wieczor-Retman
2026-03-02 20:59 ` Borislav Petkov
2026-03-02 21:22 ` Maciej Wieczor-Retman
2026-03-03 5:59 ` Borislav Petkov [this message]
2026-03-09 23:47 ` Sohil Mehta
2026-03-10 10:49 ` Maciej Wieczor-Retman
2026-03-02 15:25 ` [PATCH v8 2/3] x86/cpu: Check if feature string is non-zero Maciej Wieczor-Retman
2026-03-10 6:23 ` Sohil Mehta
2026-03-10 12:29 ` Maciej Wieczor-Retman
2026-03-02 15:25 ` [PATCH v8 3/3] x86/cpu: Do a sanity check on required feature bits Maciej Wieczor-Retman
2026-03-10 7:05 ` Sohil Mehta
2026-03-10 13:06 ` Maciej Wieczor-Retman
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=D5F67944-7C7B-4675-A495-E30CCCD4A606@alien8.de \
--to=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=farrah.chen@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.wieczorretman@pm.me \
--cc=maciej.wieczor-retman@intel.com \
--cc=mingo@redhat.com \
--cc=stable@vger.kernel.org \
--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®