public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	cl@linux-foundation.org, hannes@cmpxchg.org, mpm@selenic.com,
	npiggin@suse.de, yinghai@kernel.org
Subject: Re: [GIT PULL] Early boot SLAB for 2.6.31
Date: Wed, 10 Jun 2009 23:58:52 +0300	[thread overview]
Message-ID: <4A301E8C.8070602@cs.helsinki.fi> (raw)
In-Reply-To: <20090610205749.GA9321@elte.hu>

Ingo Molnar wrote:
> How about this: i can send the scheduler and x86 bits to Linus right 
> now, that should make it possible to have a clean base for you and 
> no interactions with anything pending?

Sure, we can do that too. Whatever works for you guys, it's not a huge 
deal for me to rebase the series.

			Pekka

  reply	other threads:[~2009-06-10 21:03 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10 20:12 [GIT PULL] Early boot SLAB for 2.6.31 Pekka J Enberg
2009-06-10 20:32 ` Linus Torvalds
2009-06-10 20:30   ` Pekka Enberg
2009-06-10 20:43     ` Ingo Molnar
2009-06-10 20:47       ` Pekka Enberg
2009-06-10 20:50         ` Ingo Molnar
2009-06-10 20:57           ` Ingo Molnar
2009-06-10 20:58             ` Pekka Enberg [this message]
2009-06-10 21:07             ` Pekka Enberg
2009-06-11  0:54               ` Ingo Molnar
2009-06-10 21:00           ` Pekka J Enberg
2009-06-10 20:33   ` Linus Torvalds
2009-06-10 20:57     ` Pekka J Enberg
2009-06-11 11:17     ` [GIT PULL v2] " Pekka J Enberg
2009-06-11 11:35       ` Ingo Molnar
2009-06-11 11:40         ` Ingo Molnar
2009-06-11 11:42           ` Ingo Molnar
2009-06-11 11:48             ` Ingo Molnar
2009-06-11 11:56               ` Pekka Enberg
2009-06-11 11:49           ` Pekka J Enberg
2009-06-11 11:54         ` Ingo Molnar
2009-06-11 13:58       ` Christoph Lameter
2009-06-11 14:06         ` Pekka Enberg
2009-06-11 14:26           ` Christoph Lameter
2009-06-11 15:24           ` Pekka Enberg
2009-06-11 17:50             ` Yinghai Lu
2009-06-11 18:10               ` [GIT PULL v3] " Pekka J Enberg
2009-06-11 21:43                 ` Ingo Molnar
2009-06-11 22:03                   ` Ingo Molnar
2009-06-11 22:41                     ` Yinghai Lu
2009-06-12  8:33                       ` Pekka Enberg
2009-06-12  7:17                     ` Ingo Molnar
2009-06-12  7:25                       ` Li Zefan
2009-06-12  7:29                       ` Pekka Enberg
2009-06-12  7:29                         ` KAMEZAWA Hiroyuki
2009-06-12  7:33                         ` Li Zefan
2009-06-12  7:51                         ` Ingo Molnar
2009-06-11 23:14                   ` Yinghai Lu
2009-06-12  8:37                     ` Pekka Enberg
2009-06-10 21:00 ` [GIT PULL] " Ingo Molnar
2009-06-10 20:57   ` Pekka Enberg
2009-06-10 21:03   ` Yinghai Lu
2009-06-10 21:11   ` Yinghai Lu

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=4A301E8C.8070602@cs.helsinki.fi \
    --to=penberg@cs.helsinki.fi \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mpm@selenic.com \
    --cc=npiggin@suse.de \
    --cc=torvalds@linux-foundation.org \
    --cc=yinghai@kernel.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