[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72mNWBTTwg0a-+V02eV3u3qKA-sBMrxsrvk=yPERg0p3EA@mail.gmail.com>
Date: Wed, 31 May 2023 19:03:19 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
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>, Gary Guo <gary@...yguo.net>,
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 0/3] Rust 1.68.2 upgrade
On Tue, Apr 18, 2023 at 11:44 PM Miguel Ojeda <ojeda@...nel.org> wrote:
>
> This is the first upgrade to the Rust toolchain since the initial Rust
> merge, from 1.62.0 to 1.68.2 (i.e. the latest).
>
> Please see the last patch message for a long explanation of the upgrade,
> the policy for future upgrades and some indications on how to easily
> review this.
>
> The series is based on `rust-next`.
Applied to `rust-next` (with the `core_ffi_c` removal in the `uapi` crate).
Thanks a lot to all reviewers and testers (and thanks Gary for
re-reviewing our diff with respect to upstream `alloc`).
Cheers,
Miguel
Powered by blists - more mailing lists