public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: linux-kernel@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Paul Mackerras <paulus@samba.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [GIT PULL 0/2] perf/core fixes
Date: Wed, 26 Sep 2012 08:58:26 +0200	[thread overview]
Message-ID: <20120926065826.GA32601@gmail.com> (raw)
In-Reply-To: <1348583839-4264-1-git-send-email-acme@infradead.org>


* Arnaldo Carvalho de Melo <acme@infradead.org> wrote:

> Hi Ingo,
> 
> 	Please consider pulling, on top of the previous req,
> 
> - Arnaldo
> 
> The following changes since commit b1ac754b67b5a875d63bee880f60ccb0c6bd8899:
> 
>   tools lib traceevent: Handle alloc_arg failure (2012-09-24 12:31:52 -0300)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux tags/perf-core-for-mingo
> 
> for you to fetch changes up to f1b2256d66fe8d613b9afcc1c16079362f9fc05c:
> 
>   tools lib traceevent: Fix error path on pevent_parse_event (2012-09-25 09:53:53 -0300)
> 
> ----------------------------------------------------------------
> perf/core fixes:
> 
> . The new perf_evsel__tp_sched_test 'perf test' broke the build by setting the
>   'ret' variable but not using it, caught by newer gcc
>   -Werror=unused-but-set-variable, fix from Namhyung Kim.
> 
> . pevent_parse_event should return a proper PEVENT_ERRNO__ and call
>   pevent_free_format on its failure path, fixes from Namhyung Kim.
> 
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> 
> ----------------------------------------------------------------
> Namhyung Kim (2):
>       perf test: Fix build failure
>       tools lib traceevent: Fix error path on pevent_parse_event
> 
>  tools/lib/traceevent/event-parse.c |    8 ++++----
>  tools/perf/builtin-test.c          |    4 ++--
>  2 files changed, 6 insertions(+), 6 deletions(-)

Pulled, thanks Arnaldo!

	Ingo

  parent reply	other threads:[~2012-09-26  6:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25 14:37 [GIT PULL 0/2] perf/core fixes Arnaldo Carvalho de Melo
2012-09-25 14:37 ` [PATCH 1/2] perf test: Fix build failure Arnaldo Carvalho de Melo
2012-09-25 14:37 ` [PATCH 2/2] tools lib traceevent: Fix error path on pevent_parse_event Arnaldo Carvalho de Melo
2012-09-26  6:58 ` Ingo Molnar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-11-03 17:11 [GIT PULL 0/2] perf/core fixes Arnaldo Carvalho de Melo
2011-11-07 18:37 ` Ingo Molnar
2011-02-23 13:36 Arnaldo Carvalho de Melo
2011-02-22  1:31 Arnaldo Carvalho de Melo
2011-02-22  7:54 ` Ingo Molnar
2010-12-01  1:19 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=20120926065826.GA32601@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@infradead.org \
    --cc=acme@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --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