From: Boqun Feng <boqun.feng@gmail.com>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: "Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Alex Gaynor" <alex.gaynor@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>,
"Masahiro Yamada" <masahiroy@kernel.org>,
linux-kbuild@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org, patches@lists.linux.dev
Subject: Re: [PATCH 2/2] rust: upgrade to Rust 1.76.0
Date: Fri, 16 Feb 2024 21:57:29 -0800 [thread overview]
Message-ID: <ZdBKycd6mPI5cpkA@boqun-archlinux> (raw)
In-Reply-To: <20240217002638.57373-2-ojeda@kernel.org>
On Sat, Feb 17, 2024 at 01:26:38AM +0100, Miguel Ojeda wrote:
> This is the next upgrade to the Rust toolchain, from 1.75.0 to 1.76.0
> (i.e. the latest) [1].
>
I've applied this on the merge point of for-next/rust-for-arm64 in arm64
tree and today's rust-next (patch #1 has a small conflict with the
target.json changes in arm64 tree), tested with kunit for both x86 and
arm64.
Tested-by: Boqun Feng <boqun.feng@gmail.com>
Regards,
Boqun
> See the upgrade policy [2] and the comments on the first upgrade in
> commit 3ed03f4da06e ("rust: upgrade to Rust 1.68.2").
>
[...]
next prev parent reply other threads:[~2024-02-17 5:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 0:26 [PATCH 1/2] kbuild: mark `rustc` (and others) invocations as recursive Miguel Ojeda
2024-02-17 0:26 ` [PATCH 2/2] rust: upgrade to Rust 1.76.0 Miguel Ojeda
2024-02-17 5:57 ` Boqun Feng [this message]
2024-02-19 9:09 ` Alice Ryhl
2024-02-19 9:52 ` [PATCH 1/2] kbuild: mark `rustc` (and others) invocations as recursive Masahiro Yamada
2024-02-29 21:33 ` 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=ZdBKycd6mPI5cpkA@boqun-archlinux \
--to=boqun.feng@gmail.com \
--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=gary@garyguo.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=ojeda@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 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.