From: Miguel Ojeda <ojeda@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"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@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 6.15 (2nd)
Date: Fri, 9 May 2025 22:14:57 +0200 [thread overview]
Message-ID: <20250509201458.872943-1-ojeda@kernel.org> (raw)
Hi Linus,
Please pull these fixes for Rust (second round).
All commits have been in linux-next for two rounds.
No conflicts expected.
Thanks!
Cheers,
Miguel
The following changes since commit 92a09c47464d040866cf2b4cd052bc60555185fb:
Linux 6.15-rc5 (2025-05-04 13:55:04 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/ojeda/linux.git tags/rust-fixes-6.15-2
for you to fetch changes up to 5595c31c370957aabe739ac3996aedba8267603f:
x86/Kconfig: make CFI_AUTO_DEFAULT depend on !RUST or Rust >= 1.88 (2025-05-07 00:11:47 +0200)
----------------------------------------------------------------
Rust fixes for v6.15 (2nd)
Toolchain and infrastructure:
- Make CFI_AUTO_DEFAULT depend on !RUST or Rust >= 1.88.0.
- Clean Rust (and Clippy) lints for the upcoming Rust 1.87.0 and Rust
1.88.0 releases.
- Clean objtool warning for the upcoming Rust 1.87.0 release by adding
one more noreturn function.
----------------------------------------------------------------
Miguel Ojeda (5):
objtool/rust: add one more `noreturn` Rust function for Rust 1.87.0
rust: allow Rust 1.87.0's `clippy::ptr_eq` lint
rust: clean Rust 1.88.0's `unnecessary_transmutes` lint
rust: clean Rust 1.88.0's warning about `clippy::disallowed_macros` configuration
rust: clean Rust 1.88.0's `clippy::uninlined_format_args` lint
Paweł Anikiel (1):
x86/Kconfig: make CFI_AUTO_DEFAULT depend on !RUST or Rust >= 1.88
.clippy.toml | 2 +-
arch/x86/Kconfig | 1 +
drivers/gpu/nova-core/gpu.rs | 2 +-
init/Kconfig | 3 ++
rust/bindings/lib.rs | 1 +
rust/kernel/alloc/kvec.rs | 3 ++
rust/kernel/list.rs | 3 ++
rust/kernel/str.rs | 46 +++++++++++++++----------------
rust/macros/kunit.rs | 13 +++------
rust/macros/module.rs | 19 ++++---------
rust/macros/paste.rs | 2 +-
rust/pin-init/internal/src/pinned_drop.rs | 3 +-
rust/uapi/lib.rs | 1 +
tools/objtool/check.c | 1 +
14 files changed, 49 insertions(+), 51 deletions(-)
next reply other threads:[~2025-05-09 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 20:14 Miguel Ojeda [this message]
2025-05-09 21:18 ` [GIT PULL] Rust fixes for 6.15 (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=20250509201458.872943-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--cc=a.hindborg@kernel.org \
--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=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.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 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).