From: Ramkumar Ramachandra <artagnon@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: David Ahern <dsahern@gmail.com>, Jiri Olsa <jolsa@redhat.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: [PATCH 0/4] perf: trivial follow-ons to --list-cmds
Date: Fri, 14 Mar 2014 23:17:50 -0400 [thread overview]
Message-ID: <1394853474-31019-1-git-send-email-artagnon@gmail.com> (raw)
Hi,
With "perf kvm: introduce --list-cmds for use by scripts" accepted,
these are trivial follow-on patches to enable the same functionality
in kmem, mem, lock, and sched.
Thanks.
Ramkumar Ramachandra (4):
perf kmem: introduce --list-cmds for use by scripts
perf mem: introduce --list-cmds for use by scripts
perf lock: introduce --list-cmds for use by scripts
perf sched: introduce --list-cmds for use by scripts
tools/perf/builtin-kmem.c | 8 +++++---
tools/perf/builtin-lock.c | 10 ++++++----
tools/perf/builtin-mem.c | 15 ++++++++-------
tools/perf/builtin-sched.c | 10 ++++++----
tools/perf/perf-completion.sh | 4 ++--
5 files changed, 27 insertions(+), 20 deletions(-)
--
1.9.rc0.1.g9d22d25
next reply other threads:[~2014-03-15 3:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 3:17 Ramkumar Ramachandra [this message]
2014-03-15 3:17 ` [PATCH 1/4] perf kmem: introduce --list-cmds for use by scripts Ramkumar Ramachandra
2014-04-17 9:57 ` [tip:perf/core] perf kmem: Introduce " tip-bot for Ramkumar Ramachandra
2014-03-15 3:17 ` [PATCH 2/4] perf mem: introduce " Ramkumar Ramachandra
2014-04-17 9:57 ` [tip:perf/core] perf mem: Introduce " tip-bot for Ramkumar Ramachandra
2014-03-15 3:17 ` [PATCH 3/4] perf lock: introduce " Ramkumar Ramachandra
2014-04-17 9:57 ` [tip:perf/core] perf lock: Introduce " tip-bot for Ramkumar Ramachandra
2014-03-15 3:17 ` [PATCH 4/4] perf sched: introduce " Ramkumar Ramachandra
2014-04-17 9:57 ` [tip:perf/core] perf sched: Introduce " tip-bot for Ramkumar Ramachandra
2014-03-15 15:49 ` [PATCH 0/4] perf: trivial follow-ons to --list-cmds David Ahern
2014-03-27 0:05 ` Ramkumar Ramachandra
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=1394853474-31019-1-git-send-email-artagnon@gmail.com \
--to=artagnon@gmail.com \
--cc=acme@redhat.com \
--cc=dsahern@gmail.com \
--cc=jolsa@redhat.com \
--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
all inboxes | Powered by JetHome®