Rust for Linux List
 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@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 (2nd)
Date: Sat,  6 Jun 2026 13:36:18 +0200	[thread overview]
Message-ID: <20260606113618.12487-1-ojeda@kernel.org> (raw)

Hi Linus,

Please pull these fixes for Rust.

They have all been in linux-next for a week or longer.

No conflicts expected.

Thanks!

Cheers,
Miguel

The following changes since commit 5d6919055dec134de3c40167a490f33c74c12581:

  Linux 7.1-rc3 (2026-05-10 14:08:09 -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-2

for you to fetch changes up to 905b06d32a52afe32fcf5f30cf298c9ea6359f11:

  rust: x86: support Rust >= 1.98.0 target spec (2026-05-30 15:38:16 +0200)

----------------------------------------------------------------
Rust fixes for v7.1 (2nd)

Toolchain and infrastructure:

 - Fix 'rustc-option' (the Makefile one) when cross-compiling that leads
   to build or boot failures in certain configs.

 - Work around a Rust compiler bug (already fixed for Rust 1.98.0) thats
   lead to boot failures in certain configs due to missing 'uwtable'
   LLVM module flags.

 - Support a Rust compiler change (starting with Rust 1.98.0) in the
   unstable target specification JSON files.

 - Forbid Rust + arm + KASAN configs, which do not build.

'kernel' crate:

 - Fix NOMMU build by adding a missing helper.

----------------------------------------------------------------
Alice Ryhl (2):
      rust: kasan/kbuild: fix rustc-option when cross-compiling
      rust: arm64: set uwtable llvm module flag for CONFIG_UNWIND_TABLES

Miguel Ojeda (1):
      rust: x86: support Rust >= 1.98.0 target spec

Nathan Chancellor (1):
      ARM: Do not select HAVE_RUST when KASAN is enabled

Shivam Kalra (1):
      rust: helpers: add is_vmalloc_addr wrapper for NOMMU builds

 Makefile                        | 3 ++-
 arch/arm/Kconfig                | 2 +-
 arch/arm64/Makefile             | 3 +++
 arch/x86/Makefile               | 4 ++++
 arch/x86/Makefile.um            | 8 ++++++++
 rust/helpers/vmalloc.c          | 6 ++++++
 scripts/Makefile.compiler       | 2 +-
 scripts/generate_rust_target.rs | 8 ++++++--
 8 files changed, 31 insertions(+), 5 deletions(-)

             reply	other threads:[~2026-06-06 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-06 11:36 Miguel Ojeda [this message]
2026-06-06 23:09 ` [GIT PULL] Rust fixes for 7.1 (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=20260606113618.12487-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox