mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Pekka Enberg <penberg@kernel.org>
Cc: David Rientjes <rientjes@google.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Matt Mackall <mpm@selenic.com>, Paul Mundt <lethal@linux-sh.org>,
	Nick Piggin <npiggin@kernel.dk>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH][GIT PULL] slob/lockdep: Fix gfp flags passed to lockdep
Date: Tue, 7 Jun 2011 12:19:48 +0200	[thread overview]
Message-ID: <20110607101948.GB21356@elte.hu> (raw)
In-Reply-To: <BANLkTikmp5CFKykBXaPUP0SBZEto1idDsA@mail.gmail.com>


* Pekka Enberg <penberg@kernel.org> wrote:

> On Tue, Jun 7, 2011 at 7:09 AM, David Rientjes <rientjes@google.com> wrote:
> >> Please pull the latest tip/lockdep/devel tree, which can be found at:
> >>
> >>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> >> tip/lockdep/devel
> >>
> >>
> >> Steven Rostedt (1):
> >>       slob/lockdep: Fix gfp flags passed to lockdep
> >
> > Shouldn't this be going into Pekka's slab tree?
> 
> That's what I'd expect, sure. :-)
> 
> However, I'm not pulling from a "tip/lockdep/devel" branch to slab.git
> so Steven needs to send this to me in patch format or Ingo picks it up
> in which case consider the patch:
> 
> Acked-by: Pekka Enberg <penberg@kernel.org>

Unless there are some dependencies i missed i think it would be 
better if you pulled this, hm?

Thanks,

	Ingo

  reply	other threads:[~2011-06-07 10:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06 14:14 Steven Rostedt
2011-06-07  4:09 ` David Rientjes
2011-06-07  6:06   ` Pekka Enberg
2011-06-07 10:19     ` Ingo Molnar [this message]
2011-06-07 11:15       ` Steven Rostedt
2011-06-07 11:51         ` Ingo Molnar
2011-06-07 12:13           ` Steven Rostedt

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=20110607101948.GB21356@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=npiggin@kernel.dk \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.com \
    --cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®