public inbox for linux-kernel@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>,
	"Wedson Almeida Filho" <wedsonaf@gmail.com>,
	"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@samsung.com>,
	"Alice Ryhl" <aliceryhl@google.com>,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Rust fixes for 6.11 (2nd)
Date: Thu,  5 Sep 2024 23:34:25 +0200	[thread overview]
Message-ID: <20240905213425.253828-1-ojeda@kernel.org> (raw)

Hi Linus,

Please pull these fixes for Rust (second round).

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

No conflicts expected. No changes to the C side.

Thanks!

Cheers,
Miguel

The following changes since commit 47ac09b91befbb6a235ab620c32af719f8208399:

  Linux 6.11-rc4 (2024-08-18 13:17:27 -0700)

are available in the Git repository at:

  https://github.com/Rust-for-Linux/linux.git tags/rust-fixes-6.11-2

for you to fetch changes up to cff56ff737e2da095ca9f228e2c5afc903bfca69:

  MAINTAINERS: update Andreas Hindborg's email address (2024-09-03 23:48:20 +0200)

----------------------------------------------------------------
Rust fixes for v6.11 (2nd)

Toolchain and infrastructure:

 - Fix builds for nightly compiler users now that 'new_uninit' was split
   into new features by using an alternative approach for the code that
   used what is now called the 'box_uninit_write' feature.

 - Allow the 'stable_features' lint to preempt upcoming warnings about
   them, since soon there will be unstable features that will become
   stable in nightly compilers.

 - Export bss symbols too.

'kernel' crate:

 - 'block' module: fix wrong usage of lockdep API.

'macros' crate:

 - Provide correct provenance when constructing 'THIS_MODULE'.

Documentation:

 - Remove unintended indentation (blockquotes) in generated output.

 - Fix a couple typos.

MAINTAINERS:

 - Remove Wedson as Rust maintainer.

 - Update Andreas' email.

----------------------------------------------------------------
Andreas Hindborg (3):
      rust: kbuild: fix export of bss symbols
      rust: block: fix wrong usage of lockdep API
      MAINTAINERS: update Andreas Hindborg's email address

Boqun Feng (1):
      rust: macros: provide correct provenance when constructing THIS_MODULE

Jon Mulder (1):
      docs: rust: remove unintended blockquote in Quick Start

Jubilee Young (1):
      rust: alloc: eschew `Box<MaybeUninit<T>>::write`

Michael Vetter (1):
      rust: kernel: fix typos in code comments

Miguel Ojeda (1):
      rust: allow `stable_features` lint

Vincent Woltmann (1):
      docs: rust: remove unintended blockquote in Coding Guidelines

Wedson Almeida Filho (1):
      MAINTAINERS: Remove Wedson as Rust maintainer

 .mailmap                                 |  1 +
 Documentation/rust/coding-guidelines.rst | 38 ++++++++++++++++----------------
 Documentation/rust/quick-start.rst       |  6 ++---
 MAINTAINERS                              |  5 ++---
 Makefile                                 |  1 +
 rust/Makefile                            |  2 +-
 rust/kernel/alloc/box_ext.rs             |  6 +++--
 rust/kernel/block/mq/gen_disk.rs         |  6 ++---
 rust/kernel/init/macros.rs               |  4 ++--
 rust/kernel/net/phy.rs                   |  2 +-
 rust/macros/module.rs                    |  6 ++++-
 11 files changed, 41 insertions(+), 36 deletions(-)

             reply	other threads:[~2024-09-05 21:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05 21:34 Miguel Ojeda [this message]
2024-09-06  3:20 ` [GIT PULL] Rust fixes for 6.11 (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=20240905213425.253828-1-ojeda@kernel.org \
    --to=ojeda@kernel.org \
    --cc=a.hindborg@samsung.com \
    --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=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=wedsonaf@gmail.com \
    /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