From: Boqun Feng <boqun.feng@gmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Lyude Paul" <lyude@redhat.com>, "Ingo Molnar" <mingo@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Will Deacon" <will@kernel.org>,
"Waiman Long" <longman@redhat.com>,
"Alex Gaynor" <alex.gaynor@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,
"Filipe Xavier" <felipe_life@live.com>
Subject: Re: [RFC 1/5] locking: MAINTAINERS: Start watching Rust locking primitives
Date: Fri, 20 Dec 2024 15:48:20 -0800 [thread overview]
Message-ID: <Z2YCRFd9DsiTWnS1@tardis.local> (raw)
In-Reply-To: <CANiq72=KA205nyWGxaFpuq-FRV9SXsimCsiZAhrsyX9dA37+rA@mail.gmail.com>
On Thu, Dec 05, 2024 at 12:39:44PM +0100, Miguel Ojeda wrote:
> On Wed, Dec 4, 2024 at 10:04 PM Boqun Feng <boqun.feng@gmail.com> wrote:
> >
> > Thanks! Yes, it'll be great to have more people watching this. And thank
> > you for the review and contribution so far, nice job!
>
> Indeed -- thanks Lyude!
>
> > I'm currently waiting for both lock maintainers and Rust maintainers
> > opinions on the particular changes on the MAINTAINERS file (for example,
> > maybe they want something similar to "RUST [ALLOC]" entry, i.e. a
> > standalone entry). My plan is to send the PR after everyone is on the
> > same page. And you're welcome to send a patch adding yourself in the
> > entry afterwards.
>
> Up to you! :)
>
> I guess it depends on whether the rest of the locking maintainers want
> to see every patch related to that (which would be great) or not,
> whether you want to have finer-grained control on who gets pinged,
> potentially different "M:" level and so on. For instance, it would
> allow you to have an explicit "L:" for the Rust for Linux list.
>
> By the way, as a third alternative, you could also consider a
> sub-entry in locking, too, i.e. "LOCKING PRIMITIVES [RUST]" as a
> middle ground, which would allow you to keep routing patches through
> locking but have the benefits of a sub-entry if you need them.
>
I will keep it as it is because I do want more reviews on Rust locking
parts from the current locking maintainers ;-). We can always change
this in the future.
> Whatever you decide:
>
> Acked-by: Miguel Ojeda <ojeda@kernel.org>
>
Thanks!
Regards,
Boqun
> Thanks!
>
> Cheers,
> Miguel
next prev parent reply other threads:[~2024-12-20 23:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 5:40 [RFC 0/5] locking: Start watching Rust locking primitives Boqun Feng
2024-11-28 5:40 ` [RFC 1/5] locking: MAINTAINERS: " Boqun Feng
2024-12-03 20:01 ` Lyude Paul
2024-12-04 21:03 ` Boqun Feng
2024-12-05 11:39 ` Miguel Ojeda
2024-12-20 23:48 ` Boqun Feng [this message]
2024-12-12 10:06 ` Peter Zijlstra
2024-12-12 16:51 ` Boqun Feng
2024-12-12 13:44 ` Ingo Molnar
2024-11-28 5:40 ` [RFC 2/5] rust: sync: Add Lock::from_raw() for Lock<(), B> Boqun Feng
2024-11-28 5:40 ` [RFC 3/5] rust: sync: Make Guard::new() public Boqun Feng
2024-11-28 5:40 ` [RFC 4/5] rust: sync: Add MutexGuard type alias Boqun Feng
2024-11-28 5:40 ` [RFC 5/5] rust: sync: Add SpinLockGuard " Boqun Feng
2024-12-03 20:04 ` [RFC 0/5] locking: Start watching Rust locking primitives Lyude Paul
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=Z2YCRFd9DsiTWnS1@tardis.local \
--to=boqun.feng@gmail.com \
--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=felipe_life@live.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=lyude@redhat.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mingo@redhat.com \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=will@kernel.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