From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: James Clark <james.clark@linaro.org>
Cc: Haiyue Wang <haiyuewa@163.com>,
linux-perf-users@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"open list:PERFORMANCE EVENTS SUBSYSTEM"
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] perf tools: Add the legacy-cache.json to .gitignore
Date: Tue, 20 Jan 2026 17:28:47 -0300 [thread overview]
Message-ID: <aW_lf4P_bRXcv5mQ@x1> (raw)
In-Reply-To: <f08a244f-864f-4e68-b448-c17ec9ff89b2@linaro.org>
On Tue, Dec 09, 2025 at 12:55:45PM +0000, James Clark wrote:
>
>
> On 08/12/2025 2:15 am, Haiyue Wang wrote:
> > The commit 0012e0fa221b ("perf jevents: Add legacy-hardware and legacy-cache json")
> > will auto-generate: "pmu-events/arch/common/common/legacy-cache.json".
> >
> > Signed-off-by: Haiyue Wang <haiyuewa@163.com>
> > ---
> > tools/perf/.gitignore | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/tools/perf/.gitignore b/tools/perf/.gitignore
> > index b64302a76144..5c59f954f52a 100644
> > --- a/tools/perf/.gitignore
> > +++ b/tools/perf/.gitignore
> > @@ -36,6 +36,7 @@ config.mak.autogen
> > util/intel-pt-decoder/inat-tables.c
> > arch/*/include/generated/
> > trace/beauty/generated/
> > +pmu-events/arch/common/common/legacy-cache.json
> > pmu-events/pmu-events.c
> > pmu-events/jevents
> > pmu-events/metric_test.log
>
> Reviewed-by: James Clark <james.clark@linaro.org>
Thanks, applied to perf-tools-next,
- Arnaldo
prev parent reply other threads:[~2026-01-20 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 2:15 [PATCH v1] perf tools: Add the legacy-cache.json to .gitignore Haiyue Wang
2025-12-09 12:55 ` James Clark
2026-01-20 20:28 ` Arnaldo Carvalho de Melo [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=aW_lf4P_bRXcv5mQ@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=haiyuewa@163.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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