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>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Tamir Duberstein" <tamird@kernel.org>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"Onur Özkan" <work@onurozkan.dev>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Rust fixes for 7.3 (2nd)
Date: Sun, 13 Sep 2026 16:58:08 +0200 [thread overview]
Message-ID: <20260913145808.28006-1-ojeda@kernel.org> (raw)
Hi Linus,
Please pull these fixes for Rust.
They have been in linux-next for at least 3 rounds (most for more).
No conflicts expected.
Thanks!
Cheers,
Miguel
The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:
Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)
are available in the Git repository at:
ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/ojeda/linux.git tags/rust-fixes-7.3-2
for you to fetch changes up to f4c3e38111fd84c2c7ae5785755f4a4d476e1cba:
rust: allow `unknown_lints` in generated bindings for Rust < 1.88 (2026-09-08 23:29:18 +0200)
----------------------------------------------------------------
Rust fixes for v7.3 (2nd)
Toolchain and infrastructure:
- Work around a 'bindgen' 0.73.2 bug that emits an 'allow' attribute
for 'unnecessary_transmutes', which is unknown in older compilers.
- Clean 'clippy::as_underscore' lints in generated code by the new
'bindgen' 0.73.0+ releases.
- Clean new 'clippy::needless_range_loop' lint for the upcoming Rust
1.100.0 (expected 2026-11-12).
'kernel' crate:
- 'num' module: fix soundness issue in 'Bounded' by sealing the
'Integer' trait.
'pin-init' crate:
- Fix unreachable warning for the upcoming Rust 1.100.0 (expected
2026-11-12) due to 'Infallible' becoming an alias of '!'.
Samples:
- Add missing newlines in 'pr_*!'s macro calls.
----------------------------------------------------------------
Gary Guo (1):
rust: pin-init: use irrefutable pattern for `stack_pin_init`
John Hubbard (1):
rust: allow `clippy::as_underscore` in the generated bindings
Mehmet Koseoglu (1):
rust: samples: add missing newlines in rust_print_main
Miguel Ojeda (2):
drm/panic: clean new `clippy::needless_range_loop` lint for Rust 1.100.0
rust: allow `unknown_lints` in generated bindings for Rust < 1.88
Younes Akhouayri (1):
rust: num: seal Integer
drivers/gpu/drm/drm_panic_qr.rs | 4 ++--
rust/bindings/lib.rs | 4 +++-
rust/kernel/num.rs | 9 ++++++++-
rust/pin-init/src/lib.rs | 8 +-------
rust/uapi/lib.rs | 4 +++-
samples/rust/rust_print_main.rs | 8 ++++----
6 files changed, 21 insertions(+), 16 deletions(-)
next reply other threads:[~2026-09-13 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 14:58 Miguel Ojeda [this message]
2026-09-13 17:37 ` [GIT PULL] Rust fixes for 7.3 (2nd) 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=20260913145808.28006-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=torvalds@linux-foundation.org \
--cc=work@onurozkan.dev \
/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.