From: Miguel Ojeda <ojeda@kernel.org>
To: Miguel Ojeda <ojeda@kernel.org>,
Wedson Almeida Filho <wedsonaf@gmail.com>,
Alex Gaynor <alex.gaynor@gmail.com>
Cc: "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>,
"Josh Stone" <jistone@redhat.com>,
"William Brown" <william.brown@suse.com>,
"Georgy Yakovlev" <gyakovlev@gentoo.org>,
"Jan Alexander Steffens" <jan.steffens@gmail.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev
Subject: [PATCH 0/3] Rust 1.68.2 upgrade
Date: Tue, 18 Apr 2023 23:43:44 +0200 [thread overview]
Message-ID: <20230418214347.324156-1-ojeda@kernel.org> (raw)
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`.
Miguel Ojeda (3):
rust: alloc: clarify what is the upstream version
rust: arc: fix intra-doc link in `Arc<T>::init`
rust: upgrade to Rust 1.68.2
Documentation/process/changes.rst | 2 +-
rust/alloc/README.md | 3 +
rust/alloc/alloc.rs | 55 ++--
rust/alloc/boxed.rs | 446 ++++++++++++++++++++++++++--
rust/alloc/collections/mod.rs | 5 +-
rust/alloc/lib.rs | 71 +++--
rust/alloc/raw_vec.rs | 16 +-
rust/alloc/slice.rs | 447 ++++------------------------
rust/alloc/vec/drain.rs | 81 +++++-
rust/alloc/vec/drain_filter.rs | 60 +++-
rust/alloc/vec/into_iter.rs | 125 ++++++--
rust/alloc/vec/is_zero.rs | 96 ++++++-
rust/alloc/vec/mod.rs | 464 +++++++++++++++++++++++-------
rust/alloc/vec/set_len_on_drop.rs | 5 +
rust/alloc/vec/spec_extend.rs | 63 +---
rust/bindings/lib.rs | 1 -
rust/kernel/build_assert.rs | 2 +
rust/kernel/init.rs | 5 +
rust/kernel/lib.rs | 4 -
rust/kernel/std_vendor.rs | 2 +
rust/kernel/sync/arc.rs | 2 +-
scripts/Makefile.build | 2 +-
scripts/min-tool-version.sh | 2 +-
23 files changed, 1278 insertions(+), 681 deletions(-)
--
2.40.0
next reply other threads:[~2023-04-18 21:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 21:43 Miguel Ojeda [this message]
2023-04-18 21:43 ` [PATCH 1/3] rust: alloc: clarify what is the upstream version Miguel Ojeda
2023-04-19 2:51 ` Martin Rodriguez Reboredo
2023-04-19 8:06 ` Benno Lossin
2023-04-19 11:58 ` Gary Guo
2023-04-20 12:14 ` Björn Roy Baron
2023-04-18 21:43 ` [PATCH 2/3] rust: arc: fix intra-doc link in `Arc<T>::init` Miguel Ojeda
2023-04-19 2:51 ` Martin Rodriguez Reboredo
2023-04-19 8:11 ` Benno Lossin
2023-04-19 11:59 ` Gary Guo
2023-04-20 12:15 ` Björn Roy Baron
2023-04-18 21:43 ` [PATCH 3/3] rust: upgrade to Rust 1.68.2 Miguel Ojeda
2023-04-19 3:02 ` Martin Rodriguez Reboredo
2023-05-31 17:02 ` Miguel Ojeda
2023-05-31 19:48 ` Martin Rodriguez Reboredo
2023-05-31 21:30 ` Miguel Ojeda
2023-04-19 12:38 ` Gary Guo
2023-04-20 12:31 ` Björn Roy Baron
2023-04-18 22:17 ` [PATCH 0/3] Rust 1.68.2 upgrade Miguel Ojeda
2023-04-20 3:23 ` Boqun Feng
2023-04-20 3:45 ` David Gow
2023-04-20 13:12 ` Ariel Miculas
2023-04-20 13:19 ` Miguel Ojeda
2023-04-20 17:17 ` Ariel Miculas
2023-04-20 17:20 ` Miguel Ojeda
2023-05-04 22:27 ` Fabien Parent
2023-05-05 9:59 ` Miguel Ojeda
2023-05-31 17:03 ` 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=20230418214347.324156-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=gyakovlev@gentoo.org \
--cc=jan.steffens@gmail.com \
--cc=jistone@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.com \
--cc=william.brown@suse.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 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.