From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Clark Williams <williams@redhat.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCHES 000/343] perf tools improvements and fixes for v7.2
Date: Tue, 23 Jun 2026 16:26:59 -0300 [thread overview]
Message-ID: <ajreA1h8TeG93myW@x1> (raw)
In-Reply-To: <CAHk-=wh=P369M9juK_Q8nzzTAFXy31BdizDeVFx1RTGGzaTXHw@mail.gmail.com>
On Tue, Jun 23, 2026 at 12:01:45PM -0700, Linus Torvalds wrote:
> On Mon, 22 Jun 2026 at 12:22, Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools.git tags/perf-tools-for-v7.2-1-2026-06-22
>
> This may be pre-existing and I just happened to notice now:
>
> Untracked files:
> (use "git add <file>..." to include in what will be committed)
> tools/perf/bench/bpf_skel/bench_uprobe.skel.h
>
> that's after a plain build.
>
> I've pulled this, but you need to be more careful and fix the
> .gitignore files for generated content.
>
> Not just because it pollutes "git status", but because we have a
> history of people carelessly committing stuff they shouldn't, and then
> there's even more cleanup required.
I'll add checks for this, thanks for reporting and for merging it
anyway,
- Arnaldo
prev parent reply other threads:[~2026-06-23 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 19:21 [PATCHES 000/343] perf tools improvements and fixes for v7.2 Arnaldo Carvalho de Melo
2026-06-23 19:01 ` Linus Torvalds
2026-06-23 19:26 ` 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=ajreA1h8TeG93myW@x1 \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.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=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=williams@redhat.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