[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230419125847.2083dbf5.gary@garyguo.net>
Date: Wed, 19 Apr 2023 12:58:47 +0100
From: Gary Guo <gary@...yguo.net>
To: Miguel Ojeda <ojeda@...nel.org>
Cc: Wedson Almeida Filho <wedsonaf@...il.com>,
Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...il.com>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>,
Josh Stone <jistone@...hat.com>,
William Brown <william.brown@...e.com>,
Georgy Yakovlev <gyakovlev@...too.org>,
Jan Alexander Steffens <jan.steffens@...il.com>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
patches@...ts.linux.dev
Subject: Re: [PATCH 1/3] rust: alloc: clarify what is the upstream version
On Tue, 18 Apr 2023 23:43:45 +0200
Miguel Ojeda <ojeda@...nel.org> wrote:
> It may be unclear for readers which upstream Rust version these files
> are based on. They may be unaware that they are intended to match the
> minimum (and only, so far) supported version of Rust in the kernel.
>
> Thus clarify it.
>
> Signed-off-by: Miguel Ojeda <ojeda@...nel.org>
Reviewed-by: Gary Guo <gary@...yguo.net>
> ---
> rust/alloc/README.md | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/rust/alloc/README.md b/rust/alloc/README.md
> index c89c753720b5..eb6f22e94ebf 100644
> --- a/rust/alloc/README.md
> +++ b/rust/alloc/README.md
> @@ -10,6 +10,9 @@ upstream. In general, only additions should be performed (e.g. new
> methods). Eventually, changes should make it into upstream so that,
> at some point, this fork can be dropped from the kernel tree.
>
> +The Rust upstream version on top of which these files are based matches
> +the output of `scripts/min-tool-version.sh rustc`.
> +
>
> ## Rationale
>
Powered by blists - more mailing lists