From: John Garry <john.garry@huawei.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
<linux-kernel@vger.kernel.org>, <linuxarm@huawei.com>,
<will@kernel.org>, <mark.rutland@arm.com>,
<zhangshaokun@hisilicon.com>, James Clark <James.Clark@arm.com>,
Ganapatrao Kulkarni <gklkml16@gmail.com>,
"William Cohen" <wcohen@redhat.com>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH 0/4] HiSilicon hip08 uncore PMU events additions
Date: Mon, 7 Oct 2019 14:40:39 +0100 [thread overview]
Message-ID: <6990f60b-2df4-b20c-2777-090bc4d9b6db@huawei.com> (raw)
In-Reply-To: <20191004190639.GB5399@kernel.org>
>
>> As an alternative, how about just add a maintainers entry for reviewers per
>> arch? As a start, I don't mind being added there for arm64:
>>
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -12767,6 +12767,10 @@ F: arch/*/events/*
>> F: arch/*/events/*/*
>> F: tools/perf/
>>
>> +PERFORMANCE EVENTS SUBSYSTEM ARM64 PMU EVENTS
>> +R: John Garry <john.garry@huawei.com>
>> +F: tools/perf/pmu-events/arch/arm64
>> +
>>
>> Patches per-arch should have some nod/tag from a member of the respective
>> list. Or at very least be cc'ed :)
>
> Another Ok, please send a formal patch, and it would be really nice if
> the other ARM folks would... Ack that ;-) :-) And provide extra entries
> for the other pmu-events directories or even for specific files, which
> is a possibility, right?
ok, can do. Will has kindly agreed to have his name added to the
MAINTAINERS entry (thanks). Other Cc's from ARM community may also be
interested to be included - shout if so.
So I'll just include tools/perf/pmu-events/arch/arm64 for now.
The code in tools/perf/pmu-events/. should be generic for all
architectures, while I'd say tools/perf/arch/arm64 is not strictly related.
Thanks,
John
>
> On my side I'll script a bit more and make sure that a post commit hook
> warns me if the right tag is not present.
>
> - Arnaldo
>
> .
>
next prev parent reply other threads:[~2019-10-07 13:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 15:54 John Garry
2019-09-04 15:54 ` [PATCH 1/4] perf jevents: Fix Hisi hip08 DDRC PMU eventname John Garry
2019-10-21 23:19 ` [tip: perf/core] perf vendor events arm64: " tip-bot2 for John Garry
2019-09-04 15:54 ` [PATCH 2/4] perf jevents: Add some missing events for Hisi hip08 DDRC PMU John Garry
2019-10-21 23:19 ` [tip: perf/core] perf vendor events arm64: " tip-bot2 for John Garry
2019-09-04 15:54 ` [PATCH 3/4] perf jevents: Add some missing events for Hisi hip08 L3C PMU John Garry
2019-10-21 23:19 ` [tip: perf/core] perf vendor events arm64: " tip-bot2 for John Garry
2019-09-04 15:54 ` [PATCH 4/4] perf jevents: Add some missing events for Hisi hip08 HHA PMU John Garry
2019-10-21 23:19 ` [tip: perf/core] perf vendor events arm64: " tip-bot2 for John Garry
2019-10-04 14:30 ` [PATCH 0/4] HiSilicon hip08 uncore PMU events additions John Garry
2019-10-04 14:36 ` Arnaldo Carvalho de Melo
2019-10-04 14:38 ` Arnaldo Carvalho de Melo
2019-10-04 14:59 ` Will Deacon
2019-10-04 14:59 ` John Garry
2019-10-04 15:18 ` Arnaldo Carvalho de Melo
2019-10-04 16:30 ` John Garry
2019-10-04 19:06 ` Arnaldo Carvalho de Melo
2019-10-07 13:40 ` John Garry [this message]
2019-10-09 1:14 ` Shaokun Zhang
2019-10-15 15:16 ` Arnaldo Carvalho de Melo
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=6990f60b-2df4-b20c-2777-090bc4d9b6db@huawei.com \
--to=john.garry@huawei.com \
--cc=James.Clark@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=arnaldo.melo@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=gklkml16@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=wcohen@redhat.com \
--cc=will@kernel.org \
--cc=zhangshaokun@hisilicon.com \
/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®