From: Ingo Molnar <mingo@elte.hu>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: linux-kernel@vger.kernel.org, David Ahern <daahern@cisco.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Lin Ming <ming.m.lin@intel.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Mike Galbraith <efault@gmx.de>, Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Tom Zanussi <tzanussi@gmail.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [GIT PULL 0/3] perf/core improvements and fixes
Date: Wed, 30 Mar 2011 09:10:48 +0200 [thread overview]
Message-ID: <20110330071048.GB24029@elte.hu> (raw)
In-Reply-To: <1301452532-1260-1-git-send-email-acme@infradead.org>
* Arnaldo Carvalho de Melo <acme@infradead.org> wrote:
> Hi Ingo,
>
> Please consider pulling from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux-2.6 perf/core
>
> This one has everything in acme/perf/urgent, i.e. starts the next
> tools/ devel cycle :-)
>
> Regards,
>
> - Arnaldo
>
> Arnaldo Carvalho de Melo (1):
> perf tools: Fixup exit path when not able to open events
>
> David Ahern (1):
> perf tools: Emit clearer message for sys_perf_event_open ENOENT
> return
>
> Lin Ming (1):
> perf probe: Add fastpath to do lookup by function name
>
> tools/perf/builtin-record.c | 19 +++++++---
> tools/perf/builtin-top.c | 44 ++++++++++++++++--------
> tools/perf/util/debug.c | 10 +++++
> tools/perf/util/debug.h | 1 +
> tools/perf/util/probe-finder.c | 72 ++++++++++++++++++++++++++++++++++++++++
> tools/perf/util/probe-finder.h | 2 +
> 6 files changed, 128 insertions(+), 20 deletions(-)
Pulled, thanks Arnaldo!
Note, i merged these two also into perf/urgent:
ca6a42586fae: perf tools: Emit clearer message for sys_perf_event_open ENOENT return
c286c419c784: perf tools: Fixup exit path when not able to open events
as both are simple and fix real bugs.
Thanks,
Ingo
next prev parent reply other threads:[~2011-03-30 7:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 2:35 [GIT PULL 0/3] perf/core improvements and fixes Arnaldo Carvalho de Melo
2011-03-30 2:35 ` [PATCH 1/3] perf tools: Fixup exit path when not able to open events Arnaldo Carvalho de Melo
2011-03-30 2:35 ` [PATCH 2/3] perf tools: Emit clearer message for sys_perf_event_open ENOENT return Arnaldo Carvalho de Melo
2011-03-30 2:35 ` [PATCH 3/3] perf probe: Add fastpath to do lookup by function name Arnaldo Carvalho de Melo
2011-03-30 7:10 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-27 21:18 [GIT PULL 0/3] perf/core improvements and fixes Arnaldo Carvalho de Melo
2012-09-28 7:50 ` Ingo Molnar
2011-02-08 22:09 Arnaldo Carvalho de Melo
2011-02-08 22:09 Arnaldo Carvalho de Melo
2011-01-04 17:18 Arnaldo Carvalho de Melo
2011-01-05 13:11 ` Ingo Molnar
2011-01-05 13:14 ` Ingo Molnar
2011-01-05 15:48 ` Arnaldo Carvalho de Melo
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=20110330071048.GB24029@elte.hu \
--to=mingo@elte.hu \
--cc=acme@ghostprotocols.net \
--cc=acme@infradead.org \
--cc=daahern@cisco.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=ming.m.lin@intel.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tzanussi@gmail.com \
/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