From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Stephane Eranian <eranian@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [GIT PULL] perf tools updates
Date: Sun, 22 May 2011 14:07:34 +0200 [thread overview]
Message-ID: <20110522120731.GA1728@nowhere> (raw)
In-Reply-To: <20110522084934.GB27167@elte.hu>
On Sun, May 22, 2011 at 10:49:34AM +0200, Ingo Molnar wrote:
>
> * Frederic Weisbecker <fweisbec@gmail.com> wrote:
>
> > Ingo, Arnaldo,
> >
> > Please pull the perf/core branch that can be found at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
> > perf/core
> >
> > Thanks,
> > Frederic
> > ---
> >
> > Frederic Weisbecker (6):
> > perf tools: Check we are able to read the event size on mmap
> > perf tools: Remove junk code in mmap size handling
> > perf tools: Move evlist sample helpers to evlist area
> > perf tools: Pre-check sample size before parsing
> > perf tools: Robustify dynamic sample content fetch
> > perf tools: Propagate event parse error handling
> >
> >
> > tools/perf/builtin-test.c | 9 ++++++++-
> > tools/perf/builtin-top.c | 7 ++++++-
> > tools/perf/util/event.c | 16 ++++++++++++++++
> > tools/perf/util/event.h | 12 +++++++++++-
> > tools/perf/util/evlist.c | 31 +++++++++++++++++++++++++++++++
> > tools/perf/util/evlist.h | 3 +++
> > tools/perf/util/evsel.c | 32 +++++++++++++++++++++++++++++++-
> > tools/perf/util/header.c | 31 -------------------------------
> > tools/perf/util/header.h | 2 --
> > tools/perf/util/python.c | 13 ++++++++++---
> > tools/perf/util/session.c | 25 ++++++++++++++++++-------
> > tools/perf/util/session.h | 2 ++
> > 12 files changed, 136 insertions(+), 47 deletions(-)
>
> To get this upstream ASAP i pulled them into perf/urgent and resolved two
> conflicts there (a contextual and a semantic one) - please double check my
> resolutions.
Yeah looks good.
Thanks!
next prev parent reply other threads:[~2011-05-22 12:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 1:45 [GIT PULL] perf tools updates Frederic Weisbecker
2011-05-22 1:45 ` [PATCH 1/6] perf tools: Check we are able to read the event size on mmap Frederic Weisbecker
2011-05-22 1:45 ` [PATCH 2/6] perf tools: Remove junk code in mmap size handling Frederic Weisbecker
2011-05-22 1:45 ` [PATCH 4/6] perf tools: Pre-check sample size before parsing Frederic Weisbecker
2011-05-22 1:45 ` [PATCH 5/6] perf tools: Robustify dynamic sample content fetch Frederic Weisbecker
2011-05-22 1:45 ` [PATCH 6/6] perf tools: Propagate event parse error handling Frederic Weisbecker
2011-05-22 8:49 ` [GIT PULL] perf tools updates Ingo Molnar
2011-05-22 12:07 ` Frederic Weisbecker [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-29 23:34 Frederic Weisbecker
2011-07-01 10:01 ` Ingo Molnar
2010-04-24 2:05 Frederic Weisbecker
2010-04-24 2:27 ` Frederic Weisbecker
2010-04-27 9:15 ` 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=20110522120731.GA1728@nowhere \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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).