All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boqun Feng <boqun.feng@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Ingo Molnar" <mingo@redhat.com>,
	"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,
	"Lyude Paul" <lyude@redhat.com>,
	"Filipe Xavier" <felipe_life@live.com>
Subject: Re: [RFC 1/5] locking: MAINTAINERS: Start watching Rust locking primitives
Date: Thu, 12 Dec 2024 08:51:10 -0800	[thread overview]
Message-ID: <Z1sUfudkQzZLdLiX@boqun-archlinux> (raw)
In-Reply-To: <20241212100641.GW21636@noisy.programming.kicks-ass.net>

On Thu, Dec 12, 2024 at 11:06:41AM +0100, Peter Zijlstra wrote:
> On Wed, Nov 27, 2024 at 09:40:18PM -0800, Boqun Feng wrote:
> > It makes sense to add Rust locking primitives under the watch of general
> > locking primitives maintainers. This will encourage more reviews and
> > find potential issues earlier. Hence add related Rust files into the
> > LOCKING PRIMITIVES entry in MAINTAINERS.
> > 
> > While we are at it, change the role of myself into the maintainer of
> > LOCKDEP and RUST to reflect my responsibility for the corresponding
> > code.
> > 
> > Signed-off-by: Boqun Feng <boqun.feng@gmail.com>
> 
> This seems fine with me; thanks for taking that up Boqun. I'm assuming
> this whole series is aimed at the rust tree, in which case:
> 
> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> 

Thanks! Actually I'm planning to combine this series into my upcoming PR
to tip, the PR candidate is something like:

	https://git.kernel.org/pub/scm/linux/kernel/git/boqun/linux.git/log/?h=lockdep-for-tip

(I still need a few days to catch up with other locking patches, so
probably after -rc3)

Would this (targeting tip/locking/core) work for you?

Regards,
Boqun

> > ---
> >  MAINTAINERS | 7 ++++++-
> >  1 file changed, 6 insertions(+), 1 deletion(-)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 443217066eb9..3a6a193fad99 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -13351,8 +13351,8 @@ LOCKING PRIMITIVES
> >  M:	Peter Zijlstra <peterz@infradead.org>
> >  M:	Ingo Molnar <mingo@redhat.com>
> >  M:	Will Deacon <will@kernel.org>
> > +M:	Boqun Feng <boqun.feng@gmail.com> (LOCKDEP & RUST)
> >  R:	Waiman Long <longman@redhat.com>
> > -R:	Boqun Feng <boqun.feng@gmail.com> (LOCKDEP)
> >  L:	linux-kernel@vger.kernel.org
> >  S:	Maintained
> >  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/core
> > @@ -13366,6 +13366,11 @@ F:	include/linux/seqlock.h
> >  F:	include/linux/spinlock*.h
> >  F:	kernel/locking/
> >  F:	lib/locking*.[ch]
> > +F:	rust/helpers/mutex.c
> > +F:	rust/helpers/spinlock.c
> > +F:	rust/kernel/sync/lock.rs
> > +F:	rust/kernel/sync/lock/
> > +F:	rust/kernel/sync/locked_by.rs
> >  X:	kernel/locking/locktorture.c
> >  
> >  LOGICAL DISK MANAGER SUPPORT (LDM, Windows 2000/XP/Vista Dynamic Disks)
> > -- 
> > 2.39.5 (Apple Git-154)
> > 

  reply	other threads:[~2024-12-12 16:51 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
2024-12-12 10:06   ` Peter Zijlstra
2024-12-12 16:51     ` Boqun Feng [this message]
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=Z1sUfudkQzZLdLiX@boqun-archlinux \
    --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=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 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.