public inbox for rust-for-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
	Alex Gaynor <alex.gaynor@gmail.com>,
	Miguel Ojeda <ojeda@kernel.org>
Cc: kernel-team@android.com, "Will Deacon" <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <benno.lossin@proton.me>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
	patches@lists.linux.dev, stable@vger.kernel.org,
	"Matthew Maurer" <mmaurer@google.com>,
	"Ralf Jung" <post@ralfj.de>,
	"Jubilee Young" <workingjubilee@gmail.com>
Subject: Re: [PATCH] arm64: rust: clean Rust 1.85.0 warning using softfloat target
Date: Thu, 13 Feb 2025 13:59:03 +0000	[thread overview]
Message-ID: <173944714987.2610867.13703061512287477883.b4-ty@kernel.org> (raw)
In-Reply-To: <20250210163732.281786-1-ojeda@kernel.org>

On Mon, 10 Feb 2025 17:37:32 +0100, Miguel Ojeda wrote:
> Starting with Rust 1.85.0 (to be released 2025-02-20), `rustc` warns
> [1] about disabling neon in the aarch64 hardfloat target:
> 
>     warning: target feature `neon` cannot be toggled with
>              `-Ctarget-feature`: unsound on hard-float targets
>              because it changes float ABI
>       |
>       = note: this was previously accepted by the compiler but
>               is being phased out; it will become a hard error
>               in a future release!
>       = note: for more information, see issue #116344
>               <https://github.com/rust-lang/rust/issues/116344>
> 
> [...]

Applied to arm64 (for-next/fixes), thanks!

[1/1] arm64: rust: clean Rust 1.85.0 warning using softfloat target
      https://git.kernel.org/arm64/c/446a8351f160

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev

  parent reply	other threads:[~2025-02-13 13:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 16:37 [PATCH] arm64: rust: clean Rust 1.85.0 warning using softfloat target Miguel Ojeda
2025-02-11 10:33 ` Will Deacon
2025-02-13 12:22   ` Miguel Ojeda
2025-02-11 11:10 ` Trevor Gross
2025-02-12  0:57   ` Matthew Maurer
2025-02-12  7:34   ` Ralf Jung
2025-02-12  9:27 ` Alice Ryhl
2025-02-13 13:59 ` Will Deacon [this message]
2025-02-13 15:32 ` Ard Biesheuvel
2025-02-13 15:46   ` Ralf Jung
2025-02-13 17:12     ` Gary Guo
2025-02-13 17:18     ` Ard Biesheuvel
2025-02-13 20:17       ` Ralf Jung

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=173944714987.2610867.13703061512287477883.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=a.hindborg@kernel.org \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=gary@garyguo.net \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmaurer@google.com \
    --cc=ojeda@kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=post@ralfj.de \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tmgross@umich.edu \
    --cc=workingjubilee@gmail.com \
    /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