All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Nathan Chancellor <nathan@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 10:29:38 +0100	[thread overview]
Message-ID: <av7BgoDGvN15sdNq@gmail.com> (raw)
In-Reply-To: <20261119041205.GA1218811@ax162>


* Nathan Chancellor <nathan@kernel.org> wrote:

> On Wed, Nov 18, 2026 at 07:16:35PM -0800, Borislav Petkov wrote:
> > On Mon, Nov 16, 2026 at 01:45:17PM -0700, Nathan Chancellor wrote:
> > > Hmmm, not a bad idea. That does seems to work based on my initial tests,
> > 
> > So I'm going to zap what I had queued until we figure out what we really wanna
> > do here.
> 
> If there are no objections, I'll send v3 within the next few days. Let's
> take it for 7.5 instead of 7.4 just to give it time to soak, I don't
> think this is really high priority (and I am testing -next most of the
> time anyways).

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
trying to do something about it. Sorry about penalizing your diligence. :-)

Thanks,

	Ingo


  parent reply	other threads:[~2026-11-19  9:29 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 [this message]
2026-11-19 19:21               ` Nathan Chancellor
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=av7BgoDGvN15sdNq@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=nathan@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.