From: Miguel Ojeda <ojeda@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Rust fixes for 7.1
Date: Sat, 9 May 2026 19:04:12 +0200 [thread overview]
Message-ID: <20260509170412.45089-1-ojeda@kernel.org> (raw)
Hi Linus,
Please pull these fixes for Rust.
They have been in linux-next this full week.
No conflicts expected.
I will likely send another fixes PR later in the cycle.
Thanks!
Cheers,
Miguel
The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:
Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/ojeda/linux.git tags/rust-fixes-7.1
for you to fetch changes up to 2adc8664018c1cc595c7c0c98474a33c7fe32a85:
rust: allow `clippy::collapsible_if` globally (2026-04-30 23:21:31 +0200)
----------------------------------------------------------------
Rust fixes for v7.1
Toolchain and infrastructure:
- Add 'bindgen' target to make UML 32-bit builds work with GCC.
- Disable two Clippy warnings ('collapsible_{if,match}').
'pin-init' crate:
- Fix unsoundness issue that created &'static references.
----------------------------------------------------------------
David Gow (1):
rust: arch: um: Fix building 32-bit UML with GCC
Gary Guo (2):
rust: pin-init: internal: move alignment check to `make_field_check`
rust: pin-init: fix incorrect accessor reference lifetime
Miguel Ojeda (2):
rust: allow `clippy::collapsible_match` globally
rust: allow `clippy::collapsible_if` globally
Makefile | 2 +
drivers/android/binder/range_alloc/array.rs | 1 -
rust/Makefile | 2 +
rust/pin-init/internal/src/init.rs | 184 +++++++++++++---------------
rust/pin-init/src/__internal.rs | 28 +++--
5 files changed, 107 insertions(+), 110 deletions(-)
next reply other threads:[~2026-05-09 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 17:04 Miguel Ojeda [this message]
2026-05-09 18:39 ` [GIT PULL] Rust fixes for 7.1 pr-tracker-bot
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=20260509170412.45089-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=torvalds@linux-foundation.org \
/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.