From: Nathan Chancellor <nathan@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
stable@vger.kernel.org, x86@kernel.org
Subject: Re: [tip: x86/urgent] x86/build: Do not allow X86_NATIVE_CPU to be enabled when compile testing
Date: Thu, 19 Nov 2026 12:21:39 -0700 [thread overview]
Message-ID: <20261119192139.GA875856@ax162> (raw)
In-Reply-To: <av7BgoDGvN15sdNq@gmail.com>
On Thu, Nov 19, 2026 at 10:29:38AM +0100, Ingo Molnar wrote:
> Sounds good to me (and v2 looks pretty good as well) - and this bug
> is pretty old, so you are probaby the first one to trigger it and
Yeah, I did a little more digging for the upstream report [1] and it is
definitely an odd corner case, so I am not surprised this has not been
noticed before :)
> trying to do something about it. Sorry about penalizing your diligence. :-)
Eh, I don't see it as penalized, coming to a solution everyone is happy
with is just part of the process. Thanks again for all the discussion to
get there.
--
Cheers,
Nathan
next prev parent reply other threads:[~2026-11-19 19:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 6:05 [tip: x86/urgent] x86/build: Do not allow X86_NATIVE_CPU to be enabled when compile testing tip-bot2 for Nathan Chancellor
2026-11-16 9:40 ` Ingo Molnar
2026-11-16 13:01 ` Nathan Chancellor
2026-11-16 15:48 ` Linus Torvalds
2026-11-16 15:53 ` Linus Torvalds
2026-11-16 20:45 ` Nathan Chancellor
2026-11-19 3:16 ` Borislav Petkov
2026-11-19 4:12 ` Nathan Chancellor
2026-11-19 5:19 ` Borislav Petkov
2026-11-19 9:29 ` Ingo Molnar
2026-11-19 19:21 ` Nathan Chancellor [this message]
2026-11-16 22:36 ` David Laight
2026-11-18 7:28 ` Nathan Chancellor
2026-11-18 9:00 ` David Laight
2026-11-19 4:17 ` Nathan Chancellor
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=20261119192139.GA875856@ax162 \
--to=nathan@kernel.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.