mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Clark <james.clark@arm.com>
To: gregkh@linuxfoundation.org, coresight@lists.linaro.org,
	suzuki.poulose@arm.com, mike.leach@linaro.org,
	linux-kernel@vger.kernel.org
Cc: leo.yan@linaro.org, namhyung@kernel.org,
	atrajeev@linux.vnet.ibm.com, James Clark <james.clark@arm.com>
Subject: [PATCH v2] MAINTAINERS: coresight: Add missing Coresight files
Date: Fri, 20 Oct 2023 16:41:03 +0100	[thread overview]
Message-ID: <20231020154103.55936-1-james.clark@arm.com> (raw)

There are a few files missing from the list like test_arm_coresight.sh
and arm-coresight.txt so add the missing entries.

Signed-off-by: James Clark <james.clark@arm.com>
---

Changes since V1: 
 * Don't wildcard everything so that habanalabs/gaudi/gaudi_coresight*
   isn't included.

Link to V1: https://lore.kernel.org/lkml/20231005084001.34741-1-james.clark@arm.com/

 MAINTAINERS | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 7a7bd8bd80e9..6b0e21ab7d00 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2068,12 +2068,16 @@ F:	Documentation/trace/coresight/*
 F:	drivers/hwtracing/coresight/*
 F:	include/dt-bindings/arm/coresight-cti-dt.h
 F:	include/linux/coresight*
+F:	include/uapi/linux/coresight*
 F:	samples/coresight/*
+F:	tools/perf/Documentation/arm-coresight.txt
 F:	tools/perf/arch/arm/util/auxtrace.c
 F:	tools/perf/arch/arm/util/cs-etm.c
 F:	tools/perf/arch/arm/util/cs-etm.h
 F:	tools/perf/arch/arm/util/pmu.c
+F:	tools/perf/tests/shell/*coresight*
 F:	tools/perf/tests/shell/coresight/*
+F:	tools/perf/tests/shell/lib/*coresight*
 F:	tools/perf/util/cs-etm-decoder/*
 F:	tools/perf/util/cs-etm.*
 
-- 
2.34.1


                 reply	other threads:[~2023-10-20 15:41 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=20231020154103.55936-1-james.clark@arm.com \
    --to=james.clark@arm.com \
    --cc=atrajeev@linux.vnet.ibm.com \
    --cc=coresight@lists.linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=leo.yan@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.leach@linaro.org \
    --cc=namhyung@kernel.org \
    --cc=suzuki.poulose@arm.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®