public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	sfi-devel@simplefirmware.org
Subject: Re: linux-next: Tree for June 19
Date: Tue, 23 Jun 2009 02:34:07 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.0906230227250.5879@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.0906201415400.4083@localhost.localdomain>

>>> git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-sfi-2.6.git sfi-test

>>> A description of the project is on the SFI home page: 
>>> http://simplefirmware.org/

>> Is this 2.6.31 or 32 material?

Hi Stephen,

On second though, I'll wait for 2.6.32 merge window to push upstream.

So go ahead and delay pulling sfi-test until after 2.6.31-rc1 is declared.

thanks,
-Len Brown, Intel Open Source Technology Center

  parent reply	other threads:[~2009-06-23  7:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19  7:26 linux-next: Tree for June 19 Stephen Rothwell
2009-06-19 13:44 ` Nico -telmich- Schottelius
2009-06-19 17:38 ` [PATCH -next] dm: dm-log-userspace depends on NET Randy Dunlap
2009-06-19 18:31   ` Jonathan Brassow
2009-06-19 18:24 ` [PATCH -next] dm: fix dm-log-userspace printk format Randy Dunlap
2009-06-19 18:32   ` Jonathan Brassow
2009-06-20  4:16 ` linux-next: Tree for June 19 Len Brown
2009-06-20  5:04   ` Stephen Rothwell
2009-06-20  5:12     ` Stephen Rothwell
2009-06-20 18:27     ` Len Brown
2009-06-21 15:54       ` Stephen Rothwell
2009-06-29  5:25         ` Stephen Rothwell
2009-06-29  7:14         ` Ingo Molnar
2009-06-29  7:30           ` Stephen Rothwell
2009-06-23  6:34       ` Len Brown [this message]
2009-06-23  8:54         ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2008-06-19  8:05 Stephen Rothwell

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=alpine.LFD.2.00.0906230227250.5879@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfi-devel@simplefirmware.org \
    --cc=sfr@canb.auug.org.au \
    /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