From: David Ahern <dsahern@gmail.com>
To: acme@ghostprotocols.net, linux-kernel@vger.kernel.org
Cc: David Ahern <dsahern@gmail.com>
Subject: [PATCH 0/4] perf: remove unused functions
Date: Tue, 12 Mar 2013 23:07:24 -0600 [thread overview]
Message-ID: <1363151248-16674-1-git-send-email-dsahern@gmail.com> (raw)
Hi Arnaldo:
Going through my backlog of perf cleanup patches. These remove unused
functions and then makes a sole callee static.
David Ahern (4):
perf: remove unused print_event function
perf: remove unused print_trace_event function
perf: remove unused perf_session__remove_thread
perf: move machine__remove_thread and make static
tools/perf/util/machine.c | 22 ++++++++++-----------
tools/perf/util/machine.h | 1 -
tools/perf/util/session.c | 12 ------------
tools/perf/util/session.h | 1 -
tools/perf/util/trace-event-parse.c | 37 -----------------------------------
tools/perf/util/trace-event.h | 4 ----
6 files changed, 11 insertions(+), 66 deletions(-)
--
1.7.10.1
next reply other threads:[~2013-03-13 5:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 5:07 David Ahern [this message]
2013-03-13 5:07 ` [PATCH 1/4] perf: remove unused print_event function David Ahern
2013-03-13 5:07 ` [PATCH 2/4] perf: remove unused print_trace_event function David Ahern
2013-03-21 11:27 ` [tip:perf/core] perf tools: Remove unused tracing functions tip-bot for David Ahern
2013-03-13 5:07 ` [PATCH 3/4] perf: remove unused perf_session__remove_thread David Ahern
2013-03-21 11:28 ` [tip:perf/core] perf session: Remove unused perf_session__remove_thread method tip-bot for David Ahern
2013-03-13 5:07 ` [PATCH 4/4] perf: move machine__remove_thread and make static David Ahern
2013-03-21 11:30 ` [tip:perf/core] perf machine: Move " tip-bot for David Ahern
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=1363151248-16674-1-git-send-email-dsahern@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.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).