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>,
"Andreas Hindborg" <a.hindborg@samsung.com>,
"Alice Ryhl" <aliceryhl@google.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev
Subject: [PATCH 0/3] Rust 1.73.0 upgrade
Date: Thu, 5 Oct 2023 23:05:52 +0200 [thread overview]
Message-ID: <20231005210556.466856-1-ojeda@kernel.org> (raw)
This is the next upgrade to the Rust toolchain since the initial Rust
merge, from 1.72.1 to 1.73.0 (i.e. the latest, released today).
Please see the main 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: task: remove redundant explicit link
rust: print: use explicit link in documentation
rust: upgrade to Rust 1.73.0
Documentation/process/changes.rst | 2 +-
rust/alloc/alloc.rs | 22 --------------
rust/alloc/boxed.rs | 48 ++++++++++++++++++++-----------
rust/alloc/lib.rs | 5 ++--
rust/alloc/raw_vec.rs | 30 ++++++++++++-------
rust/alloc/vec/mod.rs | 4 +--
rust/alloc/vec/spec_extend.rs | 8 +++---
rust/compiler_builtins.rs | 1 +
rust/kernel/print.rs | 1 +
rust/kernel/task.rs | 2 +-
scripts/min-tool-version.sh | 2 +-
11 files changed, 65 insertions(+), 60 deletions(-)
base-commit: b2516f7af9d238ebc391bdbdae01ac9528f1109e
--
2.42.0
next reply other threads:[~2023-10-05 21:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 21:05 Miguel Ojeda [this message]
2023-10-05 21:05 ` [PATCH 1/3] rust: task: remove redundant explicit link Miguel Ojeda
2023-10-05 21:29 ` Martin Rodriguez Reboredo
2023-10-06 8:17 ` Finn Behrens
2023-10-06 8:51 ` Alice Ryhl
2023-10-09 8:48 ` Vincenzo Palazzo
2023-10-05 21:05 ` [PATCH 2/3] rust: print: use explicit link in documentation Miguel Ojeda
2023-10-05 21:30 ` Martin Rodriguez Reboredo
2023-10-06 8:14 ` Finn Behrens
2023-10-06 8:52 ` Alice Ryhl
2023-10-09 8:48 ` Vincenzo Palazzo
2023-10-05 21:05 ` [PATCH 3/3] rust: upgrade to Rust 1.73.0 Miguel Ojeda
2023-10-05 21:30 ` Martin Rodriguez Reboredo
2023-10-06 9:08 ` Alice Ryhl
2023-10-09 8:49 ` Vincenzo Palazzo
2023-10-15 19:35 ` [PATCH 0/3] Rust 1.73.0 upgrade 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=20231005210556.466856-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).