From: Thomas-Mich Richter <tmricht@linux.vnet.ibm.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: "linux-perf-use." <linux-perf-users@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Hendrik Brueckner <brueckner@linux.vnet.ibm.com>
Subject: Re: perf buildid-cache -p <path> question
Date: Thu, 26 Oct 2017 09:07:21 +0200 [thread overview]
Message-ID: <2b863f9e-e3f3-fa7f-7014-679d7fac63ea@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171026015723.6d9202ce81b2fb222993f63b@kernel.org>
On 10/25/2017 06:57 PM, Masami Hiramatsu wrote:
...
>>
>> When you look at the patch I submitted, in function build_id_cache__purge_path()
>> you specify a fully qualified path name, for example /usr/bin/tar. This is a file
>> and it calls function build_id_cache__remove_file() to remove its entries in the cache.
>
> OK, now I see what the question is based on...
> I'll see your patch.
>
> Thank you,
>
I think we drop the patch and change the man page instead.
Any objections?
--
Thomas Richter, Dept 3303, IBM LTC Boeblingen Germany
--
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
next prev parent reply other threads:[~2017-10-26 7:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 12:24 perf buildid-cache -p <path> question Thomas-Mich Richter
2017-10-16 13:45 ` Thomas-Mich Richter
2017-10-16 14:12 ` Arnaldo Carvalho de Melo
2017-10-20 16:12 ` Masami Hiramatsu
2017-10-20 16:20 ` Arnaldo Carvalho de Melo
2017-10-24 7:56 ` Thomas-Mich Richter
2017-10-25 17:04 ` Masami Hiramatsu
2017-10-26 7:05 ` Thomas-Mich Richter
2017-10-21 15:17 ` Masami Hiramatsu
2017-10-24 6:50 ` Thomas-Mich Richter
2017-10-25 16:57 ` Masami Hiramatsu
2017-10-26 7:07 ` Thomas-Mich Richter [this message]
2017-10-26 14:41 ` Masami Hiramatsu
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=2b863f9e-e3f3-fa7f-7014-679d7fac63ea@linux.vnet.ibm.com \
--to=tmricht@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=brueckner@linux.vnet.ibm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mhiramat@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;
as well as URLs for NNTP newsgroup(s).