linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	LKML <linux-kernel@vger.kernel.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [GIT PULL v3] perf fixes
Date: Sat, 3 Apr 2010 12:38:34 +0200	[thread overview]
Message-ID: <20100403103829.GC5172@nowhere> (raw)
In-Reply-To: <20100402173203.GA11712@elte.hu>

On Fri, Apr 02, 2010 at 07:32:03PM +0200, Ingo Molnar wrote:
> 
> * Frederic Weisbecker <fweisbec@gmail.com> wrote:
> 
> > On Wed, Mar 31, 2010 at 05:58:45AM +0200, Frederic Weisbecker wrote:
> > > Ingo,
> > > 
> > > Please pull the perf/urgent branch that can be found at:
> > > 
> > > git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
> > > 	perf/urgent
> > 
> > 
> > I have updated the tree. There was a leftover patch for perf/core
> > inside (not listed here). Also, since you've merged linus tree in
> > perf/urgent lately, I've zapped my merge commit. Other than that,
> > the three fixes remain.
> > 
> > Thanks.
> 
> Pulled, thanks Frederic!
> 
> Note, i also queued up this patch from Edwin:
> 
>   257ef9d: perf, x86: Fix callgraphs of 32-bit processes on 64-bit kernels
> 
> with your Acked-by added.
> 
> Thanks,
> 
> 	Ingo


Ah ok. I was too cautious and eventually queued it for perf/core, but
if you think it's fine, no problem.

Thanks.


      reply	other threads:[~2010-04-03 10:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31  3:58 [GIT PULL v2] perf fixes Frederic Weisbecker
2010-03-31  3:58 ` [PATCH 1/2 v2] perf: Use hot regs with software sched switch/migrate events Frederic Weisbecker
2010-03-31  3:58 ` [PATCH 2/2] x86,kgdb: Always initialize the hw breakpoint attribute Frederic Weisbecker
2010-04-01  7:17 ` [GIT PULL v3] perf fixes Frederic Weisbecker
2010-04-02 17:32   ` Ingo Molnar
2010-04-03 10:38     ` Frederic Weisbecker [this message]

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=20100403103829.GC5172@nowhere \
    --to=fweisbec@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.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).