From: Joe Perches <joe@perches.com>
To: paulmck@kernel.org, quic_neeraju@quicinc.com, frederic@kernel.org
Cc: linux-kernel@vger.kernel.org, rcu@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add Frederic and Neeraj to their RCU files
Date: Wed, 01 Dec 2021 08:42:11 -0800 [thread overview]
Message-ID: <b5a72137f2f412e0794987ff1f03adee93ffc92a.camel@perches.com> (raw)
In-Reply-To: <20211201143312.GA3103715@paulmck-ThinkPad-P17-Gen-1>
On Wed, 2021-12-01 at 06:33 -0800, Paul E. McKenney wrote:
> Adding Frederic as an RCU maintainer for kernel/rcu/tree_nocb.h given his
> work with offloading and de-offloading callbacks from CPUs. Also adding
> Neeraj for kernel/rcu/tasks.h given his focused work on RCU Tasks Trace.
> As in I am reasonably certain that each understands the full contents
> of the corresponding file.
[]
> diff --git a/MAINTAINERS b/MAINTAINERS
[]
> @@ -16084,6 +16084,8 @@ F: tools/testing/selftests/resctrl/
>
> READ-COPY UPDATE (RCU)
> M: "Paul E. McKenney" <paulmck@kernel.org>
> +M: Frederic Weisbecker <frederic@kernel.org> (kernel/rcu/tree_nocb.h)
> +M: Neeraj Upadhyay <quic_neeraju@quicinc.com> (kernel/rcu/tasks.h)
The words used in parentheses are email address comments and not
file matches so get_maintainer will still show them on any file
that matches the F:/X: patterns specified in the maintainers
section block.
MAINTAINERS-F: Documentation/RCU/
MAINTAINERS-F: include/linux/rcu*
MAINTAINERS-F: kernel/rcu/
MAINTAINERS-X: Documentation/RCU/torture.rst
MAINTAINERS-X: include/linux/srcu*.h
MAINTAINERS-X: kernel/rcu/srcu*.c
next prev parent reply other threads:[~2021-12-01 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 14:33 Paul E. McKenney
2021-12-01 16:42 ` Joe Perches [this message]
2021-12-01 17:10 ` Paul E. McKenney
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=b5a72137f2f412e0794987ff1f03adee93ffc92a.camel@perches.com \
--to=joe@perches.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@vger.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
all inboxes | Powered by JetHome®