From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Leo Yan <leo.yan@arm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-perf-users@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: Re: [PATCH 1/1] MAINTAINERS: Add James Clark as a perf tools reviewer
Date: Mon, 3 Nov 2025 13:30:22 -0300 [thread overview]
Message-ID: <aQjYniEKS0ZtYDEB@x1> (raw)
In-Reply-To: <CAP-5=fWcjoz_iNyMM6xSqkyDzmOmar-zaejSOn1L6Dta061kEQ@mail.gmail.com>
On Mon, Nov 03, 2025 at 08:15:45AM -0800, Ian Rogers wrote:
> On Mon, Nov 3, 2025 at 7:19 AM Leo Yan <leo.yan@arm.com> wrote:
> > On Mon, Nov 03, 2025 at 11:54:09AM -0300, Arnaldo Carvalho de Melo wrote:
> > > Just FYI, I'm carrying this on the perf tools tree.
> > > James Clark has been actively reviewing patches and contributing
> > > to perf tools. Reflect this by adding him as a reviewer in the
> > > MAINTAINERS file.
> > > Reviewed-by: James Clark <james.clark@linaro.org>
> > > Acked-by: Ingo Molnar <mingo@kernel.org>
> > > Acked-by: Namhyung Kim <namhyung@kernel.org>
> > > Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> > > Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> > Well deserved, James. Congrats!
> Great, we need more code reviews!
> Acked-by: Ian Rogers <irogers@google.com>
Thanks, added to the cset.
- Arnaldo
next prev parent reply other threads:[~2025-11-03 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 14:54 [PATCH 1/1] MAINTAINERS: Add James Clark as a perf tools reviewer Arnaldo Carvalho de Melo
2025-11-03 15:19 ` Leo Yan
2025-11-03 16:15 ` Ian Rogers
2025-11-03 16:30 ` Arnaldo Carvalho de Melo [this message]
2025-11-03 19:29 ` Peter Zijlstra
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=aQjYniEKS0ZtYDEB@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).