From: Junhao He <hejunhao3@huawei.com>
To: <peterz@infradead.org>, <mingo@redhat.com>, <acme@kernel.org>,
<namhyung@kernel.org>, <mark.rutland@arm.com>,
<alexander.shishkin@linux.intel.com>, <jolsa@kernel.org>,
<irogers@google.com>, <james.clark@linaro.org>,
<linux-perf-users@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <leo.yan@arm.com>,
<john.g.garry@oracle.com>, <will@kernel.org>,
<mike.leach@linaro.org>, <yangyicong@hisilicon.com>,
<jonathan.cameron@huawei.com>
Cc: <linuxarm@huawei.com>, <hejunhao3@huawei.com>
Subject: [PATCH 2/2] MAINTAINERS: Add hisilicon pmu json events under its entry
Date: Wed, 16 Apr 2025 10:02:16 +0800 [thread overview]
Message-ID: <20250416020216.3377959-3-hejunhao3@huawei.com> (raw)
In-Reply-To: <20250416020216.3377959-1-hejunhao3@huawei.com>
The all hisilicon pmu json events were missing to be listed there.
Signed-off-by: Junhao He <hejunhao3@huawei.com>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 00ff21b955bc..bf9588a94919 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10474,6 +10474,7 @@ W: http://www.hisilicon.com
F: Documentation/admin-guide/perf/hisi-pcie-pmu.rst
F: Documentation/admin-guide/perf/hisi-pmu.rst
F: drivers/perf/hisilicon
+F: tools/perf/pmu-events/arch/arm64/hisilicon/
HISILICON PTT DRIVER
M: Yicong Yang <yangyicong@hisilicon.com>
--
2.33.0
next prev parent reply other threads:[~2025-04-16 2:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 2:02 [PATCH 0/2] perf vendor events arm64: Add some missing content for Hisi hip08 json Junhao He
2025-04-16 2:02 ` [PATCH 1/2] perf vendor events arm64: Fill up Desc field for Hisi hip08 hha pmu Junhao He
2025-04-16 13:17 ` James Clark
2025-04-17 9:05 ` hejunhao
2025-04-16 2:02 ` Junhao He [this message]
2025-04-16 13:18 ` [PATCH 2/2] MAINTAINERS: Add hisilicon pmu json events under its entry James Clark
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=20250416020216.3377959-3-hejunhao3@huawei.com \
--to=hejunhao3@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
--cc=yangyicong@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®