public inbox for rust-for-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Miguel Ojeda <ojeda@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"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.0
Date: Sat, 21 Feb 2026 21:33:06 +0100	[thread overview]
Message-ID: <20260221203306.133927-1-ojeda@kernel.org> (raw)

Hi Linus,

Please pull these fixes for Rust.

The top commit has only been in linux-next for one round, but they are
all low risk. They are also not urgent, so they may wait for -rc2.

No conflicts expected.

Thanks!

Cheers,
Miguel

The following changes since commit 05f7e89ab9731565d8a62e3b5d1ec206485eeb0b:

  Linux 6.19 (2026-02-08 13:03:27 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/ojeda/linux.git tags/rust-fixes-7.0

for you to fetch changes up to 97b281d7edb2ae662365be2809cd728470119720:

  rust: list: Add unsafe blocks for container_of and safety comments (2026-02-20 01:59:51 +0100)

----------------------------------------------------------------
Rust fixes for v7.0-rc1

Toolchain and infrastructure:

 - Pass '-Zunstable-options' flag required by the future Rust 1.95.0.

 - Fix 'objtool' warning for Rust 1.84.0.

'kernel' crate:

 - 'irq' module: add missing bound detected by the future Rust 1.95.0.

 - 'list' module: add missing 'unsafe' blocks and placeholder safety
   comments to macros (an issue for future callers within the crate).

'pin-init' crate:

 - Clean Clippy warning that changed behavior in the future Rust 1.95.0.

----------------------------------------------------------------
Benno Lossin (2):
      rust: irq: add `'static` bounds to irq callbacks
      rust: pin-init: replace clippy `expect` with `allow`

Miguel Ojeda (2):
      rust: kbuild: pass `-Zunstable-options` for Rust 1.95.0
      objtool/rust: add one more `noreturn` Rust function

Philipp Stanner (1):
      rust: list: Add unsafe blocks for container_of and safety comments

 rust/Makefile                          |  3 +++
 rust/kernel/irq/request.rs             | 12 +++++++++---
 rust/kernel/list/impl_list_item_mod.rs | 25 ++++++++++++++++---------
 rust/pin-init/src/lib.rs               |  4 ++--
 tools/objtool/check.c                  |  3 ++-
 5 files changed, 32 insertions(+), 15 deletions(-)

             reply	other threads:[~2026-02-21 20:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-21 20:33 Miguel Ojeda [this message]
2026-02-22 20:19 ` [GIT PULL] Rust fixes for 7.0 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=20260221203306.133927-1-ojeda@kernel.org \
    --to=ojeda@kernel.org \
    --cc=a.hindborg@kernel.org \
    --cc=aliceryhl@google.com \
    --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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox