From: Alice Ryhl <aliceryhl@google.com>
To: Boqun Feng <boqun.feng@gmail.com>, Miguel Ojeda <ojeda@kernel.org>
Cc: "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
"Alice Ryhl" <aliceryhl@google.com>
Subject: [PATCH v2 0/2] Clean up Rust LockClassKey
Date: Mon, 28 Jul 2025 09:42:54 +0000 [thread overview]
Message-ID: <20250728-lock-class-key-cleanup-v2-0-ad02b80c69e1@google.com> (raw)
This series applies the suggestion from Benno [1] and various other
improvements I found when looking over the LockClassKey implementation.
Based on rust-next.
[1]: https://lore.kernel.org/all/DBIJLR7XNI6U.21PMPODHE83DZ@kernel.org/
Signed-off-by: Alice Ryhl <aliceryhl@google.com>
---
Changes in v2:
- Change safety comment to require a static object. Adjust commit
message accordingly.
- Add Reviewed-by.
- Link to v1: https://lore.kernel.org/r/20250723-lock-class-key-cleanup-v1-0-85fa506b8ca4@google.com
---
Alice Ryhl (2):
rust: sync: refactor static_lock_class!() macro
rust: sync: clean up LockClassKey and its docs
rust/kernel/sync.rs | 78 +++++++++++++++++++++++++++++++++++++++--------------
1 file changed, 58 insertions(+), 20 deletions(-)
---
base-commit: dff64b072708ffef23c117fa1ee1ea59eb417807
change-id: 20250723-lock-class-key-cleanup-a3baf53b123a
Best regards,
--
Alice Ryhl <aliceryhl@google.com>
next reply other threads:[~2025-07-28 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 9:42 Alice Ryhl [this message]
2025-07-28 9:42 ` [PATCH v2 1/2] rust: sync: refactor static_lock_class!() macro Alice Ryhl
2025-07-28 10:18 ` Benno Lossin
2025-07-28 9:42 ` [PATCH v2 2/2] rust: sync: clean up LockClassKey and its docs Alice Ryhl
2025-08-12 8:05 ` Benno Lossin
2025-08-12 15:46 ` Boqun Feng
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=20250728-lock-class-key-cleanup-v2-0-ad02b80c69e1@google.com \
--to=aliceryhl@google.com \
--cc=a.hindborg@kernel.org \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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 NNTP newsgroup(s).