public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Alice Ryhl" <aliceryhl@google.com>,
	"Alexandre Courbot" <acourbot@nvidia.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Nathan Chancellor" <nathan@kernel.org>,
	"Nicolas Schier" <nicolas.schier@linux.dev>,
	linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
	linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v2] rust: enable slice_flatten feature and provide it through an extension trait
Date: Wed, 05 Nov 2025 17:10:47 +0900	[thread overview]
Message-ID: <DE0LXMXWMDNI.WIHMY9TEPRVE@nvidia.com> (raw)
In-Reply-To: <aQoJUAdFFBpQiEZU@google.com>

On Tue Nov 4, 2025 at 11:10 PM JST, Alice Ryhl wrote:
>> diff --git a/scripts/Makefile.build b/scripts/Makefile.build
>> index d0ee33a487be..a84b9e3171a3 100644
>> --- a/scripts/Makefile.build
>> +++ b/scripts/Makefile.build
>> @@ -308,6 +308,7 @@ $(obj)/%.lst: $(obj)/%.c FORCE
>>  
>>  # The features in this list are the ones allowed for non-`rust/` code.
>>  #
>> +#   - Stable since Rust 1.80.0: `feature(slice_flatten)`.
>>  #   - Stable since Rust 1.81.0: `feature(lint_reasons)`.
>>  #   - Stable since Rust 1.82.0: `feature(asm_const)`,
>>  #     `feature(offset_of_nested)`, `feature(raw_ref_op)`.
>> @@ -317,7 +318,7 @@ $(obj)/%.lst: $(obj)/%.c FORCE
>>  #
>>  # Please see https://github.com/Rust-for-Linux/linux/issues/2 for details on
>>  # the unstable features in use.
>> -rust_allowed_features := asm_const,asm_goto,arbitrary_self_types,lint_reasons,offset_of_nested,raw_ref_op,used_with_arg
>> +rust_allowed_features := asm_const,asm_goto,arbitrary_self_types,lint_reasons,offset_of_nested,raw_ref_op,slice_flatten,used_with_arg
>
> You should double-check, but I don't think you need to list it here
> because all uses of the unstable method are under the `rust/` directory.

Confirmed that this is not needed, thank you!

      parent reply	other threads:[~2025-11-05  8:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04  3:53 [PATCH v2] rust: enable slice_flatten feature and provide it through an extension trait Alexandre Courbot
2025-11-04 14:10 ` Alice Ryhl
2025-11-04 14:15   ` Alexandre Courbot
2025-11-04 14:35     ` Alice Ryhl
2025-11-04 14:16   ` Miguel Ojeda
2025-11-05  8:10   ` Alexandre Courbot [this message]

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=DE0LXMXWMDNI.WIHMY9TEPRVE@nvidia.com \
    --to=acourbot@nvidia.com \
    --cc=a.hindborg@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=gary@garyguo.net \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=nathan@kernel.org \
    --cc=nicolas.schier@linux.dev \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox