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.9
Date: Sat, 27 Apr 2024 19:15:49 +0200 [thread overview]
Message-ID: <20240427171549.934651-1-ojeda@kernel.org> (raw)
Hi Linus,
Please pull these fixes for Rust.
There are a few that I am not sure if they should count as fixes
(trivial docs rendering, macro example and CONSTRUCTORS), so if you
prefer to see them in the merge window instead, please let me know.
The spike you will see in the diffstat is due to indentation changes,
added comments and moved lines -- the actual change is small.
Most have been in linux-next for more than a week, but the last ones
have been there only for a couple linux-next tags, and I reworded one
of those a couple days ago to add a tag (no changes otherwise -- the
original commits can be found starting at 56b70b91a161 in linux-next).
No conflicts expected. No changes to the C side.
Cheers,
Miguel
The following changes since commit 4cece764965020c22cff7665b18a012006359095:
Linux 6.9-rc1 (2024-03-24 14:10:05 -0700)
are available in the Git repository at:
https://github.com/Rust-for-Linux/linux.git tags/rust-fixes-6.9
for you to fetch changes up to 19843452dca40e28d6d3f4793d998b681d505c7f:
rust: remove `params` from `module` macro example (2024-04-25 17:34:33 +0200)
----------------------------------------------------------------
Rust fixes for v6.9
- Soundness: make internal functions generated by the 'module!' macro
inaccessible, do not implement 'Zeroable' for 'Infallible' and
require 'Send' for the 'Module' trait.
- Build: avoid errors with "empty" files and workaround 'rustdoc' ICE.
- Kconfig: depend on '!CFI_CLANG' and avoid selecting 'CONSTRUCTORS'.
- Code docs: remove non-existing key from 'module!' macro example.
- Docs: trivial rendering fix in arch table.
----------------------------------------------------------------
Alice Ryhl (1):
rust: don't select CONSTRUCTORS
Aswin Unnikrishnan (1):
rust: remove `params` from `module` macro example
Benno Lossin (1):
rust: macros: fix soundness issue in `module!` macro
Bo-Wei Chen (1):
docs: rust: fix improper rendering in Arch Support page
Conor Dooley (1):
rust: make mutually exclusive with CFI_CLANG
Laine Taffin Altman (1):
rust: init: remove impl Zeroable for Infallible
Miguel Ojeda (2):
kbuild: rust: remove unneeded `@rustc_cfg` to avoid ICE
kbuild: rust: force `alloc` extern to allow "empty" Rust files
Wedson Almeida Filho (2):
rust: phy: implement `Send` for `Registration`
rust: kernel: require `Send` for `Module` implementations
Documentation/rust/arch-support.rst | 2 +-
init/Kconfig | 2 +-
rust/Makefile | 1 -
rust/kernel/init.rs | 11 ++-
rust/kernel/lib.rs | 2 +-
rust/kernel/net/phy.rs | 4 +
rust/macros/lib.rs | 12 ---
rust/macros/module.rs | 190 ++++++++++++++++++++++--------------
scripts/Makefile.build | 2 +-
9 files changed, 132 insertions(+), 94 deletions(-)
next reply other threads:[~2024-04-27 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-27 17:15 Miguel Ojeda [this message]
2024-04-27 19:17 ` [GIT PULL] Rust fixes for 6.9 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=20240427171549.934651-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).