From: WANG Rui <r@hev.cc>
To: linux-kernel@vger.kernel.org
Cc: loongarch@lists.linux.dev, WANG Rui <r@hev.cc>
Subject: [PATCH] MAINTAINERS: Add loongarch mailing list for perf tooling
Date: Tue, 14 Apr 2026 09:33:33 +0800 [thread overview]
Message-ID: <20260414013333.15594-1-r@hev.cc> (raw)
In practice, patches touching the LoongArch-specific code under
tools/perf are not always reaching the LoongArch mailing list,
which makes it harder for the architecture maintainers to track
relevant changes.
Add the loongarch mailing list entry for the LoongArch-specific
perf tooling paths to ensure proper notification.
Signed-off-by: WANG Rui <r@hev.cc>
---
MAINTAINERS | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 3adc870d523b..4eda6355dff2 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -20720,6 +20720,11 @@ F: tools/perf/pmu-events/arch/arm64/
F: tools/perf/util/arm-spe*
F: tools/perf/util/cs-etm*
+PERFORMANCE EVENTS TOOLING LOONGARCH
+L: loongarch@lists.linux.dev
+F: tools/perf/arch/loongarch/
+F: tools/perf/util/*/*loongarch*
+
PERSONALITY HANDLING
M: Christoph Hellwig <hch@infradead.org>
L: linux-abi-devel@lists.sourceforge.net
--
2.53.0
reply other threads:[~2026-04-14 1:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260414013333.15594-1-r@hev.cc \
--to=r@hev.cc \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).