From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Paul Mackerras <paulus@samba.org>, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>, Borislav Petkov <bp@suse.de>,
Hemant Kumar <hemant@linux.vnet.ibm.com>
Subject: [perf/core PATCH v3 0/2] perf-buildid-cache: Enhance --update and add --purge
Date: Thu, 19 Feb 2015 17:08:26 +0900 [thread overview]
Message-ID: <20150219080826.2167.78265.stgit@localhost.localdomain> (raw)
Hi,
Here is the 3rd version of of perf buildid-cache update.
This has a small updates for each patch. According to
Arnaldo's comment, I updated the document about --update
option in the first patch, and renamed --remove-all to
--purge in the second patch (it also updated document).
Thank you,
---
Masami Hiramatsu (2):
perf buildid-cache: Add new buildid cache if update target is not cached
perf buildid-cache: Add --purge FILE to remove all caches of FILE
tools/perf/Documentation/perf-buildid-cache.txt | 24 ++++--
tools/perf/builtin-buildid-cache.c | 50 ++++++++++++
tools/perf/util/build-id.c | 95 +++++++++++++++++++----
tools/perf/util/build-id.h | 2
4 files changed, 146 insertions(+), 25 deletions(-)
--
Masami HIRAMATSU
Software Platform Research Dpt. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
next reply other threads:[~2015-02-19 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 8:08 Masami Hiramatsu [this message]
2015-02-19 8:08 ` [perf/core PATCH v3 1/2] perf buildid-cache: Add new buildid cache if update target is not cached Masami Hiramatsu
2015-02-19 8:08 ` [perf/core PATCH v3 2/2] perf buildid-cache: Add --purge FILE to remove all caches of FILE Masami Hiramatsu
2015-02-20 8:59 ` 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=20150219080826.2167.78265.stgit@localhost.localdomain \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=bp@suse.de \
--cc=hemant@linux.vnet.ibm.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.