From: David Ahern <dsahern@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>, Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH 0/4] perf: trivial follow-ons to --list-cmds
Date: Sat, 15 Mar 2014 09:49:01 -0600 [thread overview]
Message-ID: <5324766D.7080407@gmail.com> (raw)
In-Reply-To: <1394853474-31019-1-git-send-email-artagnon@gmail.com>
On 3/14/14, 9:17 PM, Ramkumar Ramachandra wrote:
> 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
>
All 4 look good to me.
Acked-by: David Ahern <dsahern@gmail.com>
next prev parent reply other threads:[~2014-03-15 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 3:17 Ramkumar Ramachandra
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 ` David Ahern [this message]
2014-03-27 0:05 ` [PATCH 0/4] perf: trivial follow-ons to --list-cmds 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=5324766D.7080407@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@redhat.com \
--cc=artagnon@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
Powered by JetHome