public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: James Bottomley <James.Bottomley@HansenPartnership•com>
Cc: Ingo Molnar <mingo@elte•hu>,
	Linus Torvalds <torvalds@linux-foundation•org>,
	Thomas Gleixner <tglx@linutronix•de>,
	Alan Cox <alan@lxorguk•ukuu.org.uk>,
	"H. Peter Anvin" <hpa@zytor•com>,
	Andrew Morton <akpm@linux-foundation•org>,
	linux-next@vger•kernel.org
Subject: Re: Request for linux-next inclusion of the voyager tree
Date: Thu, 11 Jun 2009 11:35:43 +1000	[thread overview]
Message-ID: <20090611113543.29528bf3.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090610165331.GA31096@elte.hu>

[-- Attachment #1: Type: text/plain, Size: 963 bytes --]

On Wed, 10 Jun 2009 18:53:31 +0200 Ingo Molnar <mingo@elte•hu> wrote:
>
> * James Bottomley <James.Bottomley@HansenPartnership•com> wrote:
> > 
> > OK, so this is an acceptable compromise for me too.
> > 
> > What I think now is needed (from me) are three patch sets:
> > 
> > 1. The final subarchitecture cleanups
> > 2. The quirk model/smp ops additions
> > 3. The voyager put back.
> 
> Yes, that looks fine.
> 
> You can have them in a single series for convenience if you want to 
> (it's probably easier for you to test that way) - but 3 separate 
> series are fine too, no strong preference either way - as long as 
> the internal structure and details follows the ordering and 
> parameters we outlined in previous mails.

OK, given this looks like a rewrite of the voyager tree, I will drop it
from linux-next for a while.

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-06-11  1:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08 16:10 Request for linux-next inclusion of the voyager tree James Bottomley
2009-06-08 23:28 ` Tony Breeds
2009-06-10 14:45   ` James Bottomley
2009-06-09  9:45 ` Stephen Rothwell
2009-06-09 13:49   ` James Bottomley
2009-06-09 20:21 ` Ingo Molnar
2009-06-09 20:33   ` James Bottomley
2009-06-09 21:18     ` Ingo Molnar
2009-06-09 23:41   ` Alan Cox
2009-06-09 23:56     ` Ingo Molnar
2009-06-10  0:04       ` Linus Torvalds
2009-06-10  0:30         ` Ingo Molnar
2009-06-10  1:00           ` Ingo Molnar
2009-06-10 14:38             ` James Bottomley
2009-06-10 15:20               ` Linus Torvalds
2009-06-10 15:28                 ` James Bottomley
2009-06-10 15:33                   ` Linus Torvalds
2009-06-10 16:19                   ` Ingo Molnar
2009-06-10 16:42               ` Ingo Molnar
2009-06-10 14:23           ` James Bottomley
2009-06-10 15:13         ` Thomas Gleixner
2009-06-10 15:23           ` Linus Torvalds
2009-06-10 15:39             ` Ingo Molnar
2009-06-10 16:02               ` James Bottomley
2009-06-10 16:53                 ` Ingo Molnar
2009-06-11  1:35                   ` Stephen Rothwell [this message]
2009-06-11  1:39                     ` James Bottomley

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=20090611113543.29528bf3.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=James.Bottomley@HansenPartnership$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=alan@lxorguk$(echo .)ukuu.org.uk \
    --cc=hpa@zytor$(echo .)com \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mingo@elte$(echo .)hu \
    --cc=tglx@linutronix$(echo .)de \
    --cc=torvalds@linux-foundation$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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