From: Alice Ryhl <aliceryhl@google.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Nathan Chancellor <nathan@kernel.org>,
Jan Polensky <japo@linux.ibm.com>,
hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com,
ojeda@kernel.org, peterz@infradead.org, jpoimboe@kernel.org,
jbaron@akamai.com, borntraeger@linux.ibm.com,
svens@linux.ibm.com, boqun@kernel.org, gary@garyguo.net,
bjorn3_gh@protonmail.com, lossin@kernel.org,
a.hindborg@kernel.org, tmgross@umich.edu, dakr@kernel.org,
rostedt@goodmis.org, ardb@kernel.org,
linux-s390@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 6/6] s390: Enable Rust support
Date: Tue, 16 Jun 2026 07:39:39 +0000 [thread overview]
Message-ID: <ajD9uw7MhsisxdzY@google.com> (raw)
In-Reply-To: <CANiq72nkm2YwxcV+vwDj+v0svd6e1dro-W_0ybVms3pG_oJiXg@mail.gmail.com>
On Mon, Jun 15, 2026 at 06:45:26PM +0200, Miguel Ojeda wrote:
> On Mon, Jun 15, 2026 at 6:40 PM Nathan Chancellor <nathan@kernel.org> wrote:
> >
> > With Rust 1.96.0, I see the following warning several times when
> > building Rust code in -next:
> >
> > warning: unstable feature specified for `-Ctarget-feature`: `backchain`
> > |
> > = note: this feature is not stably supported; its behavior can change in the future
> >
> > warning: 1 warning emitted
> >
> > I assume this is expected? If so, is there a way to silence this warning?
>
> Yes, it seems so -- please see this thread:
>
> https://lore.kernel.org/rust-for-linux/CANiq72m4GVWFYqnxNtCHTPu7XcGewHB5LNwOoayTfnXs9pPbNg@mail.gmail.com/
>
> If they are OK with it, then I guess it is fine, but it does mean CIs
> can suffer a bit from it.
Since fixing this requires a change in rustc to recognize the backchain
target feature, has this work been started? I think that for stuff like
this, we should make to at least start working on fixing the warning so
that we don't emit a warning forever.
Alice
next prev parent reply other threads:[~2026-06-16 7:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 18:14 [PATCH v6 0/6] s390: Enable Rust support and add required arch glue Jan Polensky
2026-06-08 18:14 ` [PATCH v6 1/6] s390/bug: Provide ARCH_WARN_ASM for Rust WARN/BUG support Jan Polensky
2026-06-08 18:14 ` [PATCH v6 2/6] s390/jump_label: Implement ARCH_STATIC_BRANCH_JUMP_ASM and ARCH_STATIC_BRANCH_ASM macros Jan Polensky
2026-06-08 18:14 ` [PATCH v6 3/6] rust/bindgen_parameters: Mark s390 types as opaque to prevent repr conflicts Jan Polensky
2026-06-08 18:14 ` [PATCH v6 4/6] rust: helpers: Add memchr wrapper for string operations Jan Polensky
2026-06-08 18:14 ` [PATCH v6 5/6] s390/cmpxchg: Fix KASAN stack-out-of-bounds in atomic helpers Jan Polensky
2026-06-08 18:14 ` [PATCH v6 6/6] s390: Enable Rust support Jan Polensky
2026-06-08 18:25 ` Gary Guo
2026-06-08 19:45 ` Jan Polensky
2026-06-09 13:51 ` Alexander Gordeev
2026-06-09 14:00 ` Gary Guo
2026-06-15 16:40 ` Nathan Chancellor
2026-06-15 16:45 ` Miguel Ojeda
2026-06-16 3:04 ` Nathan Chancellor
2026-06-16 7:39 ` Alice Ryhl [this message]
2026-06-16 8:45 ` Miguel Ojeda
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=ajD9uw7MhsisxdzY@google.com \
--to=aliceryhl@google.com \
--cc=a.hindborg@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=ardb@kernel.org \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=borntraeger@linux.ibm.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=japo@linux.ibm.com \
--cc=jbaron@akamai.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=nathan@kernel.org \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=svens@linux.ibm.com \
--cc=tmgross@umich.edu \
/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.