linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Will Newton <will.newton@gmail.com>
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
	kernel-janitors@vger.kernel.org, linux-next@vger.kernel.org,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [ANNOUNCE] linux-staging tree created
Date: Thu, 12 Jun 2008 16:54:41 -0700	[thread overview]
Message-ID: <20080612235441.GC4792@kroah.com> (raw)
In-Reply-To: <87a5b0800806120437n23602ba5raae500f5bd3d179f@mail.gmail.com>

On Thu, Jun 12, 2008 at 12:37:56PM +0100, Will Newton wrote:
> On Wed, Jun 11, 2008 at 5:26 PM, Greg KH <greg@kroah.com> wrote:
> > On Wed, Jun 11, 2008 at 11:45:55AM +0100, Will Newton wrote:
> >>
> >> Would the linux-staging tree be an appropriate place to merge a new
> >> architecture? Or would that be too large a change and should go via
> >> its own tree?
> >
> > That is probably too big to go into -staging and should deserve its own
> > tree based on the size of patches that have gone into creating a new
> > architecture in the past.
> 
> Our tree is about 26000 lines of diff, including a few drivers.

That's pretty sizable, I think it deserves its own tree.

> > Do you have an example of one that is currently not included in the main
> > kernel tree right now?
> 
> I have a tree that is currently about half way to public consumption,
> although I don't think there's any point pushing it until we have a
> publically available toolchain.

Yeah, that would help as well :)

thanks,

greg k-h

  reply	other threads:[~2008-06-13  0:02 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 19:05 [ANNOUNCE] linux-staging tree created Greg KH
2008-06-10 19:06 ` linux-staging status for June 10, 2008 Greg KH
2008-06-10 22:52 ` [ANNOUNCE] linux-staging tree created Theodore Tso
2008-06-10 23:05   ` Greg KH
2008-06-11  0:07 ` Felipe Balbi
2008-06-11  3:28   ` Greg KH
2008-06-11  1:05 ` Nigel Cunningham
2008-06-11  3:29   ` Greg KH
2008-06-11  4:00     ` Nigel Cunningham
2008-06-11 16:24       ` Greg KH
2008-06-11  4:03     ` Template of what you're after? (Was [ANNOUNCE] linux-staging tree created) Nigel Cunningham
2008-06-11 16:23       ` Greg KH
2008-06-11  9:27 ` [ANNOUNCE] linux-staging tree created Benny Halevy
2008-06-11  9:50   ` Boaz Harrosh
2008-06-11  9:58     ` Felipe Balbi
2008-06-11 16:25     ` Greg KH
2008-06-11 17:43       ` Boaz Harrosh
2008-06-11 16:25   ` Greg KH
2008-06-11 10:45 ` Will Newton
2008-06-11 16:26   ` Greg KH
2008-06-12 11:37     ` Will Newton
2008-06-12 23:54       ` Greg KH [this message]
2008-06-13 14:14 ` Luis R. Rodriguez
2008-06-13 14:33   ` John W. Linville
2008-06-13 15:51     ` Luis R. Rodriguez
     [not found]     ` <20080613143328.GA16506-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-06-14  0:28       ` Greg KH
     [not found]   ` <43e72e890806130714k535b041evaf750209ea492c47-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-14  0:27     ` Greg KH
2008-06-17 12:51 ` Pavel Machek
2008-07-02 23:11   ` Greg KH
2008-07-14  2:50 ` Jike Song
2008-07-14  2:56   ` Greg KH

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=20080612235441.GC4792@kroah.com \
    --to=greg@kroah.com \
    --cc=devel@linuxdriverproject.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=will.newton@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).