From: Ingo Molnar <mingo@elte.hu>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.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>,
Steven Rostedt <rostedt@goodmis.org>,
yrl.pp-manager.tt@hitachi.com, arnaldo.melo@gmail.com
Subject: Re: [GIT PULL 0/3] perf/core fixes and improvements
Date: Sun, 30 Oct 2011 12:04:53 +0100 [thread overview]
Message-ID: <20111030110453.GA3119@elte.hu> (raw)
In-Reply-To: <1319909151-11432-1-git-send-email-acme@infradead.org>
* Arnaldo Carvalho de Melo <acme@infradead.org> wrote:
> Hi Ingo,
>
> Please consider pulling from:
>
> git://github.com/acmel/linux.git perf/core
>
> Regards,
>
> - Arnaldo
>
> Arnaldo Carvalho de Melo (2):
> perf hists browser: Warn about lost events
> perf report: Add progress bar when processing time ordered events
>
> Masami Hiramatsu (1):
> perf tools: Fix a typo of command name as trace-cmd
>
> tools/perf/builtin-top.c | 41 +++++++++++++++++++++--------
> tools/perf/util/hist.h | 1 +
> tools/perf/util/session.c | 38 ++++++++++++++++++++++----
> tools/perf/util/session.h | 1 +
> tools/perf/util/top.h | 1 -
> tools/perf/util/trace-event-info.c | 2 +-
> tools/perf/util/ui/browser.c | 21 ++++++++++++---
> tools/perf/util/ui/browser.h | 3 +-
> tools/perf/util/ui/browsers/hists.c | 49 ++++++++++++++++++++++++++++++----
> 9 files changed, 127 insertions(+), 30 deletions(-)
Pulled, thanks a lot Arnaldo!
Ingo
next prev parent reply other threads:[~2011-10-30 11:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 17:25 [GIT PULL 0/3] perf/core fixes and improvements Arnaldo Carvalho de Melo
2011-10-29 17:25 ` [PATCH 1/3] perf tools: Fix a typo of command name as trace-cmd Arnaldo Carvalho de Melo
2011-10-29 17:25 ` [PATCH 2/3] perf hists browser: Warn about lost events Arnaldo Carvalho de Melo
2011-10-29 17:25 ` [PATCH 3/3] perf report: Add progress bar when processing time ordered events Arnaldo Carvalho de Melo
2011-10-30 11:04 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-19 19:12 [GIT PULL 0/3] perf/core fixes and improvements Arnaldo Carvalho de Melo
2012-03-19 19:47 ` Ingo Molnar
2012-03-19 19:56 ` Ingo Molnar
2012-03-19 20:20 ` Ingo Molnar
2012-03-19 21:17 ` Arnaldo Carvalho de Melo
2012-02-21 17:35 Arnaldo Carvalho de Melo
2012-02-22 10:12 ` Ingo Molnar
2011-12-12 13:26 Arnaldo Carvalho de Melo
2011-12-12 17:24 ` Ingo Molnar
2011-03-23 22:52 Arnaldo Carvalho de Melo
2011-03-24 8:17 ` Ingo Molnar
2010-12-22 22:36 Arnaldo Carvalho de Melo
2010-12-23 13:20 ` Ingo Molnar
2010-08-12 20:45 Arnaldo Carvalho de Melo
2010-08-04 21:26 Arnaldo Carvalho de Melo
2010-08-05 6:46 ` Ingo Molnar
2010-08-03 2:09 Arnaldo Carvalho de Melo
2010-08-03 5:44 ` Ingo Molnar
2010-07-16 18:09 Arnaldo Carvalho de Melo
2010-07-17 9:35 ` Ingo Molnar
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=20111030110453.GA3119@elte.hu \
--to=mingo@elte.hu \
--cc=acme@infradead.org \
--cc=arnaldo.melo@gmail.com \
--cc=dsahern@gmail.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=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=yrl.pp-manager.tt@hitachi.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