From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: mark.rutland@arm.com,
Mathieu Poirier <mathieu.poirier@linaro.org>,
john.garry@huawei.com, linux-kernel@vger.kernel.org,
leo.yan@linaro.org, jolsa@redhat.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] MAINTAINERS: Add entries for CoreSight and Arm SPE
Date: Fri, 21 Aug 2020 09:07:58 -0300 [thread overview]
Message-ID: <20200821120758.GE2667554@kernel.org> (raw)
In-Reply-To: <20200821090531.GC20255@willie-the-truck>
Em Fri, Aug 21, 2020 at 10:05:31AM +0100, Will Deacon escreveu:
> On Thu, Aug 20, 2020 at 11:55:10AM -0600, Mathieu Poirier wrote:
> > Add entries for perf tools elements related to the support of Arm CoreSight
> > and Arm SPE. Also lump in Arm and Arm64 architecture files to provide
> > coverage.
> >
> > Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
> > ---
> > V2:
> > - Completed fileset for SPE.
> > - Added Arm and Arm64 architecture files.
> >
> > MAINTAINERS | 8 +++++++-
> > 1 file changed, 7 insertions(+), 1 deletion(-)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index deaafb617361..e76f7bb014ce 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -13569,12 +13569,18 @@ F: kernel/events/*
> > F: tools/lib/perf/
> > F: tools/perf/
> >
> > -PERFORMANCE EVENTS SUBSYSTEM ARM64 PMU EVENTS
> > +PERFORMANCE EVENTS SUBSYSTEM ARM64
>
> I'd probably prefer to go with TOOLING instead of SUBSYSTEM, since the
> kernel parts are covered by the "ARM PMU PROFILING AND DEBUGGING" entry.
Yeah, I think its appropriate to have TOOLING instead of SUBSYSTEM, that
is more commonly used when referring to the kernel.
I'm applying with that change, locally, with your and John's Acked-by,
please holler if that is somehow controversial.
- Arnaldo
> > 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*/
> > F: tools/perf/pmu-events/arch/arm64/
> > +F: tools/perf/util/arm-spe*
> > +F: tools/perf/util/cs-etm*
>
> Either way,
>
> Acked-by: Will Deacon <will@kernel.org>
>
> Thanks,
>
> Will
--
- Arnaldo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
john.garry@huawei.com, leo.yan@linaro.org, jolsa@redhat.com,
mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] MAINTAINERS: Add entries for CoreSight and Arm SPE
Date: Fri, 21 Aug 2020 09:07:58 -0300 [thread overview]
Message-ID: <20200821120758.GE2667554@kernel.org> (raw)
In-Reply-To: <20200821090531.GC20255@willie-the-truck>
Em Fri, Aug 21, 2020 at 10:05:31AM +0100, Will Deacon escreveu:
> On Thu, Aug 20, 2020 at 11:55:10AM -0600, Mathieu Poirier wrote:
> > Add entries for perf tools elements related to the support of Arm CoreSight
> > and Arm SPE. Also lump in Arm and Arm64 architecture files to provide
> > coverage.
> >
> > Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
> > ---
> > V2:
> > - Completed fileset for SPE.
> > - Added Arm and Arm64 architecture files.
> >
> > MAINTAINERS | 8 +++++++-
> > 1 file changed, 7 insertions(+), 1 deletion(-)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index deaafb617361..e76f7bb014ce 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -13569,12 +13569,18 @@ F: kernel/events/*
> > F: tools/lib/perf/
> > F: tools/perf/
> >
> > -PERFORMANCE EVENTS SUBSYSTEM ARM64 PMU EVENTS
> > +PERFORMANCE EVENTS SUBSYSTEM ARM64
>
> I'd probably prefer to go with TOOLING instead of SUBSYSTEM, since the
> kernel parts are covered by the "ARM PMU PROFILING AND DEBUGGING" entry.
Yeah, I think its appropriate to have TOOLING instead of SUBSYSTEM, that
is more commonly used when referring to the kernel.
I'm applying with that change, locally, with your and John's Acked-by,
please holler if that is somehow controversial.
- Arnaldo
> > 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*/
> > F: tools/perf/pmu-events/arch/arm64/
> > +F: tools/perf/util/arm-spe*
> > +F: tools/perf/util/cs-etm*
>
> Either way,
>
> Acked-by: Will Deacon <will@kernel.org>
>
> Thanks,
>
> Will
--
- Arnaldo
next prev parent reply other threads:[~2020-08-21 12:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 17:55 [PATCH v2] MAINTAINERS: Add entries for CoreSight and Arm SPE Mathieu Poirier
2020-08-20 17:55 ` Mathieu Poirier
2020-08-21 8:55 ` John Garry
2020-08-21 8:55 ` John Garry
2020-08-21 9:05 ` Will Deacon
2020-08-21 9:05 ` Will Deacon
2020-08-21 12:07 ` Arnaldo Carvalho de Melo [this message]
2020-08-21 12:07 ` 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=20200821120758.GE2667554@kernel.org \
--to=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 \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.