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>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Rust fixes for 6.12
Date: Fri, 4 Oct 2024 02:03:49 +0200 [thread overview]
Message-ID: <20241004000349.675431-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, and most
for a week.
You will probably notice a non-tag base -- I used the Rust merge because
there was a trivial issue in the merge resolution so I added the fix on
top of that one without waiting for v6.12-rc1. Please let me know if you
prefer something else (e.g. I considered sending you that patch directly
to you).
No conflicts expected.
You also already merged a fix for a Rust driver (qt2025) via netdev.
Thanks!
Cheers,
Miguel
The following changes since commit 570172569238c66a482ec3eb5d766cc9cf255f69:
Merge tag 'rust-6.12' of https://github.com/Rust-for-Linux/linux (2024-09-25 10:25:40 -0700)
are available in the Git repository at:
https://github.com/Rust-for-Linux/linux.git tags/rust-fixes-6.12
for you to fetch changes up to 05cef2c4a421ca09ab9761a95e61423e59e5bfb1:
rust: kunit: use C-string literals to clean warning (2024-10-01 23:46:42 +0200)
----------------------------------------------------------------
Rust fixes for v6.12
Toolchain and infrastructure:
- Fix/improve a couple 'depends on' on the newly added CFI/KASAN
suppport to avoid build errors/warnings.
- Fix ARCH_SLAB_MINALIGN multiple definition error for RISC-V under
!CONFIG_MMU.
- Clean upcoming (Rust 1.83.0) Clippy warnings.
'kernel' crate:
- 'sync' module: fix soundness issue by requiring 'T: Sync' for
'LockedBy::access'; and fix helpers build error under PREEMPT_RT.
- Fix trivial sorting issue ('rustfmtcheck') on the v6.12 Rust merge.
----------------------------------------------------------------
Alice Ryhl (3):
rust: sync: require `T: Sync` for `LockedBy::access`
rust: KASAN+RETHUNK requires rustc 1.83.0
cfi: encode cfi normalized integers + kasan/gcov bug in Kconfig
Dirk Behme (1):
rust: mutex: fix __mutex_init() usage in case of PREEMPT_RT
Gary Guo (1):
rust: fix `ARCH_SLAB_MINALIGN` multiple definition error
Miguel Ojeda (3):
rust: kernel: sort Rust modules
rust: cfi: fix `patchable-function-entry` starting version
rust: kunit: use C-string literals to clean warning
arch/Kconfig | 18 +++++++++++++++++-
init/Kconfig | 5 +++--
rust/bindgen_parameters | 5 +++++
rust/helpers/mutex.c | 6 ++++++
rust/kernel/kunit.rs | 4 ++--
rust/kernel/lib.rs | 2 +-
rust/kernel/sync/locked_by.rs | 18 ++++++++++++++----
7 files changed, 48 insertions(+), 10 deletions(-)
next reply other threads:[~2024-10-04 0:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 0:03 Miguel Ojeda [this message]
2024-10-04 0:22 ` [GIT PULL] Rust fixes for 6.12 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=20241004000349.675431-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=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