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.14 (3rd)
Date: Sat, 15 Mar 2025 22:22:32 +0100	[thread overview]
Message-ID: <20250315212232.2360641-1-ojeda@kernel.org> (raw)

Hi Linus,

Please pull these fixes for Rust (third round).

All commits have been in linux-next for at least two rounds.

No conflicts expected.

Thanks!

Cheers,
Miguel

The following changes since commit 7eb172143d5508b4da468ed59ee857c6e5e01da6:

  Linux 6.14-rc5 (2025-03-02 11:48:20 -0800)

are available in the Git repository at:

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

for you to fetch changes up to a1eb95d6b5f4cf5cc7b081e85e374d1dd98a213b:

  scripts: generate_rust_analyzer: add uapi crate (2025-03-12 00:13:07 +0100)

----------------------------------------------------------------
Rust fixes for v6.14 (3rd)

Toolchain and infrastructure:

 - Disallow BTF generation with Rust + LTO.

 - Improve rust-analyzer support.

'kernel' crate:

 - 'init' module: remove 'Zeroable' implementation for a couple types
   that should not have it.

 - 'alloc' module: fix macOS failure in host test by satisfying POSIX
   alignment requirement.

 - Add missing '\n's to 'pr_*!()' calls.

And a couple other minor cleanups.

----------------------------------------------------------------
Alban Kurti (5):
      rust: docs: add missing newline to printing macro examples
      rust: error: add missing newline to pr_warn! calls
      rust: init: add missing newline to pr_info! calls
      rust: sync: add missing newline in locked_by log example
      rust: workqueue: add missing newline to pr_info! examples

Benno Lossin (1):
      rust: init: fix `Zeroable` implementation for `Option<NonNull<T>>` and `Option<KBox<T>>`

Matthew Maurer (1):
      rust: Disallow BTF generation with Rust + LTO

Miguel Ojeda (1):
      rust: remove leftover mentions of the `alloc` crate

Panagiotis Foliadis (1):
      rust: task: fix `SAFETY` comment in `Task::wake_up`

Tamir Duberstein (4):
      rust: alloc: satisfy POSIX alignment requirement
      scripts: generate_rust_analyzer: add missing macros deps
      scripts: generate_rust_analyzer: add missing include_dirs
      scripts: generate_rust_analyzer: add uapi crate

 Documentation/rust/quick-start.rst  |  2 +-
 Documentation/rust/testing.rst      |  2 +-
 init/Kconfig                        |  2 +-
 rust/kernel/alloc/allocator_test.rs | 18 ++++++++++
 rust/kernel/error.rs                |  2 +-
 rust/kernel/init.rs                 | 23 ++++++------
 rust/kernel/init/macros.rs          |  6 ++--
 rust/kernel/lib.rs                  |  2 +-
 rust/kernel/sync/locked_by.rs       |  2 +-
 rust/kernel/task.rs                 |  2 +-
 rust/kernel/workqueue.rs            |  6 ++--
 scripts/generate_rust_analyzer.py   | 71 ++++++++++++++++++++++---------------
 scripts/rustdoc_test_gen.rs         |  4 +--
 13 files changed, 85 insertions(+), 57 deletions(-)

             reply	other threads:[~2025-03-15 21:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-15 21:22 Miguel Ojeda [this message]
2025-03-16  1:59 ` [GIT PULL] Rust fixes for 6.14 (3rd) 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=20250315212232.2360641-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