From: Borislav Petkov <bp@alien8.de>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Chang S. Bae" <chang.seok.bae@intel.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
rust-for-linux@vger.kernel.org, tglx@kernel.org,
mingo@redhat.com, dave.hansen@linux.intel.com, hpa@zytor.com,
ojeda@kernel.org, nathan@kernel.org, boqun@kernel.org,
gary@garyguo.net, bjorn3_gh@protonmail.com, lossin@kernel.org,
a.hindborg@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
dakr@kernel.org, daniel.almeida@collabora.com, tamird@kernel.org,
acourbot@nvidia.com, work@onurozkan.dev,
Omar Avelar <omar.avelar@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] x86/build/64: Prevent native builds from generating APX instructions
Date: Wed, 2 Sep 2026 22:23:25 -0700 [thread overview]
Message-ID: <20260903052325.GKapkETZDh2AU8aWNP@fat_crate.local> (raw)
In-Reply-To: <CANiq72kT7KozY5yXyCFpN7-7rc1Rbw1cLPs-c5AFuKYVu2f4KA@mail.gmail.com>
On Mon, Aug 10, 2026 at 05:24:55PM +0200, Miguel Ojeda wrote:
> On Sat, Aug 8, 2026 at 5:21 AM Chang S. Bae <chang.seok.bae@intel.com> wrote:
> >
> > Yes, I intended “the commit” to refer to the one in the Fixes: tag. To
> > make it explicit, I can add the commit back here:
>
> > I’ll add the link to reference the status of the Rust support. Thanks.
>
> > Yes, I have included it.
>
> Thanks! With those:
>
> Acked-by: Miguel Ojeda <ojeda@kernel.org>
>
> I guess this would go through the x86 tree? Otherwise, please let me know.
I can take a v2 with feedback from this thread integrated.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2026-09-03 5:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 15:17 [PATCH v2] x86/build/64: Prevent native builds from generating APX instructions Chang S. Bae
2026-08-07 16:58 ` Miguel Ojeda
2026-08-08 3:21 ` Chang S. Bae
2026-08-10 15:24 ` Miguel Ojeda
2026-09-03 5:23 ` Borislav Petkov [this message]
2026-09-03 14:10 ` Chang S. Bae
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=20260903052325.GKapkETZDh2AU8aWNP@fat_crate.local \
--to=bp@alien8.de \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=chang.seok.bae@intel.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=dave.hansen@linux.intel.com \
--cc=gary@garyguo.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=ojeda@kernel.org \
--cc=omar.avelar@intel.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tglx@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
--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