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>,
	"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
Date: Sat, 19 Apr 2025 12:34:43 +0200	[thread overview]
Message-ID: <20250419103443.3004008-1-ojeda@kernel.org> (raw)

Hi Linus,

Please pull these fixes for Rust.

They have all been in linux-next for at least a couple rounds.

No conflicts expected.

Thanks!

Cheers,
Miguel

The following changes since commit 0af2f6be1b4281385b618cb86ad946eded089ac8:

  Linux 6.15-rc1 (2025-04-06 13:11:33 -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

for you to fetch changes up to c1b4071ec3a6a594df6c49bf8f04a60a88072525:

  rust: helpers: Add dma_alloc_attrs() and dma_free_attrs() (2025-04-15 23:06:03 +0200)

----------------------------------------------------------------
Rust fixes for v6.15

Toolchain and infrastructure:

 - Fix missing KASAN LLVM flags on first build (and fix spurious
   rebuilds) by skipping '--target'.

 - Fix Make < 4.3 build error by using '$(pound)'.

 - Fix UML build error by removing 'volatile' qualifier from io helpers.

 - Fix UML build error by adding 'dma_{alloc,free}_attrs()'  helpers.

 - Clean gendwarfksyms warnings by avoiding to export '__pfx' symbols.

 - Clean objtool warning by adding a new 'noreturn' function for 1.86.0.

 - Disable 'needless_continue' Clippy lint due to new 1.86.0 warnings.

 - Add missing 'ffi' crate to 'generate_rust_analyzer.py'.

'pin-init' crate:

 - Import a couple fixes from upstream.

----------------------------------------------------------------
FUJITA Tomonori (2):
      rust: helpers: Remove volatile qualifier from io helpers
      rust: helpers: Add dma_alloc_attrs() and dma_free_attrs()

Lukas Fischer (1):
      scripts: generate_rust_analyzer: Add ffi crate

Miguel Ojeda (6):
      rust: pin-init: alloc: restrict `impl ZeroableOption` for `Box` to `T: Sized`
      rust: pin-init: use Markdown autolinks in Rust comments
      rust: disable `clippy::needless_continue`
      rust: kasan/kbuild: fix missing flags on first build
      objtool/rust: add one more `noreturn` Rust function for Rust 1.86.0
      rust: kbuild: use `pound` to support GNU Make < 4.3

Sami Tolvanen (1):
      rust: kbuild: Don't export __pfx symbols

 MAINTAINERS                             |  1 +
 Makefile                                |  1 -
 rust/Makefile                           |  2 +-
 rust/helpers/dma.c                      | 16 ++++++++++++++++
 rust/helpers/helpers.c                  |  1 +
 rust/helpers/io.c                       | 34 ++++++++++++++++-----------------
 rust/pin-init/examples/pthread_mutex.rs |  2 +-
 rust/pin-init/src/alloc.rs              |  8 +++-----
 rust/pin-init/src/lib.rs                |  2 +-
 scripts/Makefile.compiler               |  4 ++--
 scripts/generate_rust_analyzer.py       | 12 +++++++++---
 tools/objtool/check.c                   |  1 +
 12 files changed, 53 insertions(+), 31 deletions(-)
 create mode 100644 rust/helpers/dma.c

             reply	other threads:[~2025-04-19 10:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-19 10:34 Miguel Ojeda [this message]
2025-04-19 17:22 ` [GIT PULL] Rust fixes for 6.15 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=20250419103443.3004008-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