From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Leo Yan <leo.yan@arm.com>, Mike Leach <mike.leach@arm.com>,
linux-perf-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, coresight@lists.linaro.org,
linux-kernel@vger.kernel.org, leo.yan@linaro.org,
peterz@infradead.org, mingo@redhat.com, will@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@redhat.com
Subject: Re: [PATCH 2/2] perf: tools: cs-etm: Enhance raw Coresight trace debug display
Date: Wed, 18 Mar 2026 11:45:19 -0700 [thread overview]
Message-ID: <abryv7FhSguOq929@google.com> (raw)
In-Reply-To: <abqg-uKHqobUTn3n@x1>
Hello,
On Wed, Mar 18, 2026 at 09:56:26AM -0300, Arnaldo Carvalho de Melo wrote:
> On Fri, Mar 13, 2026 at 02:45:18PM +0000, Leo Yan wrote:
> > LGTM and I tested it:
>
> > Tested-by: Leo Yan <leo.yan@arm.com>
>
> I think this is perf-tools-next material, Namhyung, please pick this
> one.
Sure, will pick up v2.
Thanks,
Namhyung
>
> Acked-by: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> Ah, BTW, this one I picked up by perusing the https://sashiko.dev list
> of reviewed patches that were CCed to linux-perf-users:
>
> https://sashiko.dev/#/?list=org.kernel.vger.linux-perf-users
>
> Thanks,
>
> - Arnaldo
prev parent reply other threads:[~2026-03-18 18:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 13:21 [PATCH 0/2] perf: tools: cs-etm: Fixes for CoreSight debug dump Mike Leach
2026-03-13 13:21 ` [PATCH 1/2] perf: tools: cs-etm: Fix print issue for Coresight debug in ETE/TRBE trace Mike Leach
2026-03-13 14:42 ` Leo Yan
2026-03-17 15:09 ` Mike Leach
2026-03-13 13:21 ` [PATCH 2/2] perf: tools: cs-etm: Enhance raw Coresight trace debug display Mike Leach
2026-03-13 14:45 ` Leo Yan
2026-03-18 12:56 ` Arnaldo Carvalho de Melo
2026-03-18 18:45 ` Namhyung Kim [this message]
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=abryv7FhSguOq929@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=coresight@lists.linaro.org \
--cc=jolsa@redhat.com \
--cc=leo.yan@arm.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox