From: Boqun Feng <boqun.feng@gmail.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>, "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
Subject: Re: [PATCH v3 0/2] Clean up Rust LockClassKey
Date: Tue, 12 Aug 2025 08:51:49 -0700 [thread overview]
Message-ID: <aJtjFRn0QKUJT-fX@Mac.home> (raw)
In-Reply-To: <20250811-lock-class-key-cleanup-v3-0-b12967ee1ca2@google.com>
On Mon, Aug 11, 2025 at 12:14:40PM +0000, Alice Ryhl wrote:
> 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>
Queued in rust-locking:
git://git.kernel.org/pub/scm/linux/kernel/git/boqun/linux.git rust-locking
For further testing and reviewing. Thanks!
Regards,
Boqun
> ---
> Changes in v3:
> - Fix duplicated "require" in commit message.
> - Mention pinning in macro safety comment.
> - Rebase on v6.17-rc1.
> - Link to v2: https://lore.kernel.org/r/20250728-lock-class-key-cleanup-v2-0-ad02b80c69e1@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: 8f5ae30d69d7543eee0d70083daf4de8fe15d585
> change-id: 20250723-lock-class-key-cleanup-a3baf53b123a
>
> Best regards,
> --
> Alice Ryhl <aliceryhl@google.com>
>
prev parent reply other threads:[~2025-08-12 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 12:14 [PATCH v3 0/2] Clean up Rust LockClassKey Alice Ryhl
2025-08-11 12:14 ` [PATCH v3 1/2] rust: sync: refactor static_lock_class!() macro Alice Ryhl
2025-08-11 12:14 ` [PATCH v3 2/2] rust: sync: clean up LockClassKey and its docs Alice Ryhl
2025-08-12 15:51 ` Boqun Feng [this message]
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=aJtjFRn0QKUJT-fX@Mac.home \
--to=boqun.feng@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.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).