All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Pekka Enberg <penberg@kernel.org>,
	David Rientjes <rientjes@google.com>,
	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 13:51:37 +0200	[thread overview]
Message-ID: <20110607115137.GA25798@elte.hu> (raw)
In-Reply-To: <1307445322.31814.23.camel@gandalf.stny.rr.com>


* Steven Rostedt <rostedt@goodmis.org> wrote:

> On Tue, 2011-06-07 at 12:19 +0200, Ingo Molnar wrote:
> > * Pekka Enberg <penberg@kernel.org> wrote:
> 
> > > 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?
> 
> Nope, this is my fault. I searched for SLOB in MAINTAINERS and didn't
> find it. But I should have looked at SLAB.
> 
> I'll resend this as a normal patch for Pekka.

Pekka could pull it as well, since you've already tested that tree 
:-)

I don't think this tree includes any other commits, right?

Thanks,

	Ingo

  reply	other threads:[~2011-06-07 11:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06 14:14 [PATCH][GIT PULL] slob/lockdep: Fix gfp flags passed to lockdep Steven Rostedt
2011-06-07  4:09 ` David Rientjes
2011-06-07  6:06   ` Pekka Enberg
2011-06-07 10:19     ` Ingo Molnar
2011-06-07 11:15       ` Steven Rostedt
2011-06-07 11:51         ` Ingo Molnar [this message]
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=20110607115137.GA25798@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.