From: Will Deacon <will@kernel.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
John Garry <john.garry@huawei.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Leo Yan <leo.yan@linaro.org>, Jiri Olsa <jolsa@redhat.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] MAINTAINERS: Add entries for CoreSight and Arm SPE
Date: Wed, 19 Aug 2020 18:30:50 +0100 [thread overview]
Message-ID: <20200819173050.GA18091@willie-the-truck> (raw)
In-Reply-To: <CANLsYkw2aBJmrHV+8_bDUtgD-Jfvndqz2kOfNNcBBMM+vztkug@mail.gmail.com>
On Wed, Aug 19, 2020 at 11:01:38AM -0600, Mathieu Poirier wrote:
> On Tue, 18 Aug 2020 at 11:56, John Garry <john.garry@huawei.com> wrote:
> > On 17/08/2020 20:31, Mathieu Poirier wrote:
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index 4e2698cc7e23..f9bb76baeec9 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -13427,8 +13427,18 @@ F: tools/perf/
> > > PERFORMANCE EVENTS SUBSYSTEM ARM64 PMU EVENTS
> > > R: John Garry <john.garry@huawei.com>
> > > R: Will Deacon <will@kernel.org>
> > > +R: Mathieu Poirier <mathieu.poirier@linaro.org>
> > > +R: Leo Yan <leo.yan@linaro.org>
> > > L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> > > S: Supported
> > > +F: tools/build/feature/test-libopencsd.c
> > > +F: tools/perf/arch/arm/util/auxtrace.c
> > > +F: tools/perf/arch/arm/util/cs-etm.*
> > > +F: tools/perf/arch/arm/util/pmu.c
> > > +F: tools/perf/arch/arm64/util/arm-spe.c
> > > +F: tools/perf/util/arm-spe.h
> > > +F: tools/perf/util/cs-etm-decoder/*
> > > +F: tools/perf/util/cs-etm.*
> >
> > But from the previous discussion, I thought that we wanted an entry to
> > cover all tools/perf/arch/arm64/ and other related folders. Or was it
> > just put all special interest parts (like SPE support) under one entry
> > and leave the other arm/arm64 parts to be caught by "PERFORMANCE EVENTS
> > SUBSYSTEM" entry?
>
> I do not have the time to maintain anything outside of coresight -
> listing individual files as I did removes any ambiguity on that front.
> I'm happy to add tools/perf/arch/arm and tools/perf/arch/arm64/ if you
> agree to maintain them. In that case you will have to be more
> specific about the "other related folders" you are referring to above.
None of us have time for this, hence why I think putting us all in one entry
with all of the files listed there makes the most sense; then people do
whatever they can and try to help each other out based on how much time they
have. I think that's much better than fine-grained maintainership where a
given file has a single point of failure.
So I think it should include:
tools/perf/arch/arm64/
tools/pmu-events/arch/arm64/
along with the SPE and Coresight files.
Arnaldo would still handle the patches, so this is really about giving us a
chance to review incoming patches without having to fish them out from the
lists.
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-08-19 17:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200817193140.3659956-1-mathieu.poirier@linaro.org>
2020-08-18 17:54 ` [PATCH] MAINTAINERS: Add entries for CoreSight and Arm SPE John Garry
2020-08-19 2:24 ` Leo Yan
2020-08-19 17:01 ` Mathieu Poirier
2020-08-19 17:30 ` Will Deacon [this message]
2020-08-19 19:26 ` Mathieu Poirier
2020-08-20 7:50 ` John Garry
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=20200819173050.GA18091@willie-the-truck \
--to=will@kernel.org \
--cc=acme@kernel.org \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.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