From: "Danilo Krummrich" <dakr@kernel.org>
To: "Boqun Feng" <boqun@kernel.org>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Peter Zijlstra" <peterz@infradead.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>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Will Deacon" <will@kernel.org>, "Ingo Molnar" <mingo@kernel.org>,
"Waiman Long" <longman@redhat.com>,
"Lyude Paul" <lyude@redhat.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Onur Özkan" <work@onurozkan.dev>,
"Mark Rutland" <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add RUST [SYNC] entry
Date: Thu, 16 Apr 2026 12:17:28 +0200 [thread overview]
Message-ID: <DHUI2VX00WY3.EMKKQNDXHC72@kernel.org> (raw)
In-Reply-To: <20260415232830.8128-1-boqun@kernel.org>
On Thu Apr 16, 2026 at 1:28 AM CEST, Boqun Feng wrote:
> We have two pull requests on Rust synchronization primitives with 10+
> patches in a row for recent cycles, so it makes sense to start the
> effort of handling this area as a group.
>
> Luckily for me, Gary Guo and Alice Ryhl agreed to help as
> co-maintainers, and we also have a talented group of reviewers:
>
> Lyude Paul started the SpinLockIrq work [1] and did an amazing job at
> improving the design and implementation.
>
> Daniel Almeida resolved the Lock<T: !Unpin> issue [2] and he did a fair
> amount of reviews in areas related to synchronization primitives
> already.
>
> Onur Özkan started the ww_mutex work [3] and did an amazing job at
> consolidating various design requirements and decisions.
>
> Of course, this only reflects my own knowledge, and I believe they did
> way more outside what I'm aware of ;-)
>
> Note that having this MAINTAINERS entry is meant to bring more people
> to help on the synchronization primitives in Rust, which means for patch
> submissions and design discussion, please still involve the
> corresponding maintainers (e.g. LOCKING and ATOMIC),
> scripts/get_maintainers.pl should have this covered.
>
> Link: https://lore.kernel.org/rust-for-linux/20260302232154.861916-1-lyude@redhat.com/ [1]
> Link: https://lore.kernel.org/all/20250828-lock-t-when-t-is-pinned-v2-0-b067c4b93fd6@collabora.com/ [2]
> Link: https://lore.kernel.org/rust-for-linux/20260103073554.34855-1-work@onurozkan.dev/ [3]
> Signed-off-by: Boqun Feng <boqun@kernel.org>
Acked-by: Danilo Krummrich <dakr@kernel.org>
> ---
> MAINTAINERS | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 55af015174a5..220dee78b225 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -23183,6 +23183,20 @@ T: git https://github.com/Rust-for-Linux/linux.git alloc-next
> F: rust/kernel/alloc.rs
> F: rust/kernel/alloc/
>
> +RUST [SYNC]
NIT: I think we should keep this sorted alphabetically.
> +M: Boqun Feng <boqun@kernel.org>
> +M: Gary Guo <gary@garyguo.net>
> +M: Alice Ryhl <aliceryhl@google.com>
> +R: Lyude Paul <lyude@redhat.com>
> +R: Daniel Almeida <daniel.almeida@collabora.com>
> +R: "Onur Özkan" <work@onurozkan.dev>
> +L: linux-kernel@vger.kernel.org
> +L: rust-for-linux@vger.kernel.org
> +S: Maintained
> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/boqun/linux.git rust-sync
> +F: rust/kernel/sync.rs
> +F: rust/kernel/sync/
> +
> RUST [NUM]
> M: Alexandre Courbot <acourbot@nvidia.com>
> R: Yury Norov <yury.norov@gmail.com>
> --
> 2.50.1 (Apple Git-155)
prev parent reply other threads:[~2026-04-16 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 23:28 [PATCH] MAINTAINERS: Add RUST [SYNC] entry Boqun Feng
2026-04-15 23:44 ` Daniel Almeida
2026-04-16 4:36 ` Gary Guo
2026-04-16 6:13 ` Alice Ryhl
2026-04-16 6:14 ` Onur Özkan
2026-04-16 10:17 ` Danilo Krummrich [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=DHUI2VX00WY3.EMKKQNDXHC72@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=lossin@kernel.org \
--cc=lyude@redhat.com \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=will@kernel.org \
--cc=work@onurozkan.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.