public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Mike Galbraith <efault@gmx.de>, Paul Mackerras <paulus@samba.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Stephane Eranian <eranian@google.com>,
	arnaldo.melo@gmail.com
Subject: Re: [GIT PULL 0/4] perf test improvements
Date: Fri, 02 Dec 2011 09:54:24 -0700	[thread overview]
Message-ID: <4ED902C0.5020300@gmail.com> (raw)
In-Reply-To: <1322842769-7232-1-git-send-email-acme@infradead.org>



On 12/02/2011 09:19 AM, Arnaldo Carvalho de Melo wrote:
> Hi Ingo,
> 
>         Please consider pulling from:
> 
> git://github.com/acmel/linux.git perf/core
> 
> 	Now there are 29 outstanding changesets on this branch.

What about the 2 commits on your urgent branch? I don't recall seeing a
response that those were picked up, and they are not in Linus' branch.

David


> 
> Regards,
> 
> - Arnaldo
> 
> Arnaldo Carvalho de Melo (4):
>   perf evlist: Always do automatic allocation of pollfd and mmap structures
>   perf test: Allow running just a subset of the available tests
>   perf event: Introduce perf_event__fprintf
>   perf test: Validate PERF_RECORD_ events and perf_sample fields
> 
>  tools/perf/Documentation/perf-test.txt |    8 +-
>  tools/perf/builtin-record.c            |    6 -
>  tools/perf/builtin-stat.c              |    3 +-
>  tools/perf/builtin-test.c              |  418 ++++++++++++++++++++++++++++++--
>  tools/perf/builtin-top.c               |   19 +--
>  tools/perf/util/event.c                |   54 ++++-
>  tools/perf/util/event.h                |    6 +
>  tools/perf/util/evlist.c               |    4 +-
>  tools/perf/util/evlist.h               |    2 -
>  9 files changed, 465 insertions(+), 55 deletions(-)
> 

  parent reply	other threads:[~2011-12-02 16:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02 16:19 [GIT PULL 0/4] perf test improvements Arnaldo Carvalho de Melo
2011-12-02 16:19 ` [PATCH 1/4] perf evlist: Always do automatic allocation of pollfd and mmap structures Arnaldo Carvalho de Melo
2011-12-02 16:19 ` [PATCH 2/4] perf test: Allow running just a subset of the available tests Arnaldo Carvalho de Melo
2011-12-02 16:19 ` [PATCH 3/4] perf event: Introduce perf_event__fprintf Arnaldo Carvalho de Melo
2011-12-02 16:19 ` [PATCH 4/4] perf test: Validate PERF_RECORD_ events and perf_sample fields Arnaldo Carvalho de Melo
2011-12-02 17:07   ` David Ahern
2011-12-02 19:06     ` Arnaldo Carvalho de Melo
2011-12-02 17:07   ` David Ahern
2011-12-02 16:54 ` David Ahern [this message]
2011-12-02 18:22   ` [GIT PULL 0/4] perf test improvements Arnaldo Carvalho de Melo
2011-12-05 15:46     ` Ingo Molnar
2011-12-05  9:22 ` 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=4ED902C0.5020300@gmail.com \
    --to=dsahern@gmail.com \
    --cc=acme@ghostprotocols.net \
    --cc=acme@infradead.org \
    --cc=arnaldo.melo@gmail.com \
    --cc=efault@gmx.de \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.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