From: Namhyung Kim <namhyung@kernel.org>
To: Haiyue Wang <haiyuewa@163.com>
Cc: linux-perf-users@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@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>,
"Liang, Kan" <kan.liang@linux.intel.com>,
"open list:PERFORMANCE EVENTS SUBSYSTEM"
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] perf tools: Add the empty-pmu-events build to .gitignore
Date: Tue, 5 Nov 2024 23:37:01 -0800 [thread overview]
Message-ID: <Zyscncm_MDm5Swy9@google.com> (raw)
In-Reply-To: <20241105052409.7783-1-haiyuewa@163.com>
Hello,
On Tue, Nov 05, 2024 at 01:24:05PM +0800, Haiyue Wang wrote:
> The commit 0fe881f10ceb ("perf jevents: Autogenerate empty-pmu-events.c")
> build will generate two files, add them to .gitignore:
>
> tools/perf/pmu-events/empty-pmu-events.log
> tools/perf/pmu-events/test-empty-pmu-events.c
>
> Signed-off-by: Haiyue Wang <haiyuewa@163.com>
It doesn't apply to the current perf-tools-next. Can you please rebase?
Thanks,
Namhyung
> ---
> tools/perf/.gitignore | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tools/perf/.gitignore b/tools/perf/.gitignore
> index f5b81d439387..51713b655f62 100644
> --- a/tools/perf/.gitignore
> +++ b/tools/perf/.gitignore
> @@ -39,6 +39,8 @@ trace/beauty/generated/
> pmu-events/pmu-events.c
> pmu-events/jevents
> pmu-events/metric_test.log
> +pmu-events/empty-pmu-events.log
> +pmu-events/test-empty-pmu-events.c
> tests/shell/*.shellcheck_log
> tests/shell/coresight/*.shellcheck_log
> tests/shell/lib/*.shellcheck_log
> --
> 2.47.0
>
prev parent reply other threads:[~2024-11-06 7:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 5:24 [PATCH v1] perf tools: Add the empty-pmu-events build to .gitignore Haiyue Wang
2024-11-05 5:35 ` Ian Rogers
2024-11-06 7:37 ` 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=Zyscncm_MDm5Swy9@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=haiyuewa@163.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).