From: John Garry <john.garry@huawei.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
Will Deacon <will@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Leo Yan <leo.yan@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Jiri Olsa <jolsa@redhat.com>, Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] MAINTAINERS: Add entries for CoreSight and Arm SPE
Date: Thu, 20 Aug 2020 08:50:44 +0100 [thread overview]
Message-ID: <691cdbfa-d266-ec2e-e687-3ce1ca3014d8@huawei.com> (raw)
In-Reply-To: <CANLsYkzn2yuhVzZD0p-C156qi28ukHQDa83F8pezESsptG4d1Q@mail.gmail.com>
On 19/08/2020 20:26, Mathieu Poirier wrote:
> On Wed, 19 Aug 2020 at 11:30, Will Deacon <will@kernel.org> wrote:
>>
>> 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
Maybe "PERFORMANCE EVENTS SUBSYSTEM ARM64" would be more appropriate now.
>>>>> 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.
As Leo mentioned, I was thinking of tools/perf/util/arm-spe-decoder/
>>
>> 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.
>
> Thanks for the clarification - just wanted to make sure I don't sign
> you guys up for something you didn't agree to.
And it's "R:" level, so none of the commitment associated with "M:". In
addition - and maybe most important - the linux-arm-kernel list will (or
should) be cc'ed.
>
>>
>> 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
> .
>
Cheers,
John
prev parent reply other threads:[~2020-08-20 7:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 19:31 Mathieu Poirier
2020-08-18 17:54 ` John Garry
2020-08-19 2:24 ` Leo Yan
2020-08-19 17:01 ` Mathieu Poirier
2020-08-19 17:30 ` Will Deacon
2020-08-19 19:26 ` Mathieu Poirier
2020-08-20 7:50 ` John Garry [this message]
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=691cdbfa-d266-ec2e-e687-3ce1ca3014d8@huawei.com \
--to=john.garry@huawei.com \
--cc=acme@kernel.org \
--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 \
--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
Powered by JetHome