From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Linux v5.19-rc1] tools/perf/a.out remains after make -C tools/perf clean
Date: Tue, 14 Jun 2022 16:24:49 -0300 [thread overview]
Message-ID: <YqjggY64PKfog0YW@kernel.org> (raw)
In-Reply-To: <CA+icZUWpSF6ge76JVp1qBC5QhC1AwNacs5Di=e1QSbAD+SVKUA@mail.gmail.com>
Em Tue, Jun 07, 2022 at 08:59:31PM +0200, Sedat Dilek escreveu:
> Hi,
>
> I observed this some time ago - so this is not only Linux v5.19-rc1 related.
>
> $ LC_ALL=C make -C tools/perf clean 2>&1 | tee ../make-log_perf-clean.txt
> make: Entering directory '/home/dileks/src/linux-kernel/git/tools/perf'
> CLEAN x86
> CLEAN libtraceevent
> CLEAN libapi
> CLEAN libbpf
> CLEAN libsubcmd
> CLEAN libperf
> CLEAN fixdep
> CLEAN feature-detect
> CLEAN python
> CLEAN bpf-skel
> CLEAN core-objs
> CLEAN core-progs
> CLEAN core-gen
> CLEAN Documentation
> make: Leaving directory '/home/dileks/src/linux-kernel/git/tools/perf'
>
> $ git status -s
> M tools/perf/util/unwind-libunwind-local.c
> ?? tools/perf/a.out
>
> $ rm -v tools/perf/a.out
> 'tools/perf/a.out' deleted
>
> $ git checkout -- tools/perf/util/unwind-libunwind-local.c
>
> $ git status -s
> [ empty ]
Interesting, since Linus complained at some point that after building
perf some new temp file was left there I added 'git status' to my
scripts to always get this flagged.
I'm not seeing this here.
- Arnaldo
next prev parent reply other threads:[~2022-06-14 19:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 0:08 [PATCH] perf unwind: Fix uninitialized variable Ian Rogers
2022-06-07 0:26 ` Fangrui Song
2022-06-09 16:34 ` Arnaldo Carvalho de Melo
2022-06-07 18:12 ` Sedat Dilek
2022-06-08 19:29 ` Sedat Dilek
2022-06-07 18:59 ` [Linux v5.19-rc1] tools/perf/a.out remains after make -C tools/perf clean Sedat Dilek
2022-06-14 19:24 ` Arnaldo Carvalho de Melo [this message]
2022-06-14 22:11 ` Sedat Dilek
2022-06-26 15:31 ` Arnaldo Carvalho de Melo
2022-06-27 6:20 ` Sedat Dilek
2022-06-28 14:39 ` Arnaldo Carvalho de Melo
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=YqjggY64PKfog0YW@kernel.org \
--to=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sedat.dilek@gmail.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