[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4ab2efaf-867a-4b8a-8e4a-193f8218dd33@intel.com>
Date: Thu, 6 Feb 2025 12:58:07 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Alice Ryhl <aliceryhl@...gle.com>
Cc: x86@...nel.org, rust-for-linux@...r.kernel.org,
Miguel Ojeda <ojeda@...nel.org>, Boqun Feng <boqun.feng@...il.com>,
Gary Guo <gary@...yguo.net>, Björn Roy Baron
<bjorn3_gh@...tonmail.com>, Benno Lossin <benno.lossin@...ton.me>,
Andreas Hindborg <a.hindborg@...nel.org>, Trevor Gross <tmgross@...ch.edu>,
Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
Borislav Petkov <bp@...en8.de>, Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH] x86: rust: set rustc-abi=x86-softfloat on rustc>=1.86.0
On 2/6/25 10:51, Miguel Ojeda wrote:
> x86: I will pick this up, but if x86 wants to do so, that would be
> welcome -- in which case:
>
> Acked-by: Miguel Ojeda <ojeda@...nel.org>
Hey Miguel,
Are you saying you'd prefer that we pick this up on the x86 side? I'm
totally happy to do that, and it's obviously patching x86-specific
sections of the rust scripts.
If I'm understanding the ask.... Just curious though, what makes that
preferable? It's in a rust-specific file
(scripts/generate_rust_target.rs) and I'd guess that it'd be easier to
take it through the rust tree since it's more likely to collide with
stuff there and also be closer to the folks that can competently resolve
any merge problems.
Powered by blists - more mailing lists