public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: linux-kernel@vger.kernel.org, "Anton Blanchard" <anton@samba.org>,
	"Dave Martin" <dave.martin@linaro.org>,
	"Masami Hiramatsu" <masami.hiramatsu.pt@hitachi.com>,
	"Nicolas Pitre" <nicolas.pitre@linaro.org>,
	"Srikar Dronamraju" <srikar@linux.vnet.ibm.com>,
	"Steven Rostedt" <rostedt@goodmis.org>,
	"Will Deacon" <Will.Deacon@arm.com>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
	"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [GIT PULL 0/3] perf/core fixes and improvements
Date: Thu, 5 Aug 2010 08:46:06 +0200	[thread overview]
Message-ID: <20100805064606.GA30292@elte.hu> (raw)
In-Reply-To: <1280957164-14274-1-git-send-email-acme@infradead.org>


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

> 
> Hi Ingo,
> 
>         Please pull from:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux-2.6 perf/core
> 
> Regards,
> 
> - Arnaldo
> 
> Dave Martin (1):
>   perf events: Fix mmap offset determination
> 
> Srikar Dronamraju (2):
>   perf: expose event__process function
>   tracing/kprobes: unregister_trace_probe needs to be called under mutex
> 
>  kernel/trace/trace_kprobe.c |    3 +++
>  tools/perf/builtin-top.c    |   20 --------------------
>  tools/perf/util/event.c     |   28 +++++++++++++++++++++-------
>  tools/perf/util/event.h     |    1 +
>  4 files changed, 25 insertions(+), 27 deletions(-)

Pulled, thanks a lot Arnaldo!

	Ingo

  parent reply	other threads:[~2010-08-05  6:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-04 21:26 [GIT PULL 0/3] perf/core fixes and improvements Arnaldo Carvalho de Melo
2010-08-04 21:26 ` [PATCH 1/3] perf events: Fix mmap offset determination Arnaldo Carvalho de Melo
2010-08-04 21:26 ` [PATCH 2/3] perf: expose event__process function Arnaldo Carvalho de Melo
2010-08-04 21:26 ` [PATCH 3/3] tracing/kprobes: unregister_trace_probe needs to be called under mutex Arnaldo Carvalho de Melo
2010-08-05  6:46 ` 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-10-29 17:25 Arnaldo Carvalho de Melo
2011-10-30 11:04 ` 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-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=20100805064606.GA30292@elte.hu \
    --to=mingo@elte.hu \
    --cc=Will.Deacon@arm.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@infradead.org \
    --cc=anton@samba.org \
    --cc=dave.martin@linaro.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=nicolas.pitre@linaro.org \
    --cc=rostedt@goodmis.org \
    --cc=srikar@linux.vnet.ibm.com \
    --cc=tglx@linutronix.de \
    /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