public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Can you add the staging tree to -next?
Date: Fri, 14 Nov 2008 09:32:58 -0800	[thread overview]
Message-ID: <20081114173258.GC22980@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0811140825410.11953@anakin>

On Fri, Nov 14, 2008 at 08:42:48AM +0100, Geert Uytterhoeven wrote:
> On Wed, 12 Nov 2008, Greg KH wrote:
> > I'm starting to get people sending me patches against -next for the
> > drivers/staging/ tree that don't apply as -next does not include my
> > quilt tree of staging patches.
> > 
> > Can you please pick it up?  You can put it at the end of your series,
> > and the 'make allmodconfig' option disables building anything in the
> > drivers/staging/ subdirectory, so it should not have any build or merge
> > conflicts with anything.
> 
> Apart from the patches you receive against -next, is there any other
> advantage, giving staging is disabled?

That is a huge advantage, don't discount it.  My staging tree has over
150 patches in it right now, and is quite diverged from what is in
Linus's tree.  I have been getting the same patches sent over and over
to fix the same thing that is already resolved in my tree, as the
developers are working against -next thinking that they were working
with the latest development tree.

This will save a lot of redundant developer time, a good thing.

It also lets me test -next with -staging in it so I can anticipate the
merge issues that will be happening in the next big merge (v4l is going
to have issues that I've noticed already.)

thanks,

greg k-h

  parent reply	other threads:[~2008-11-14 17:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12 23:56 Can you add the staging tree to -next? Greg KH
2008-11-13 23:44 ` Stephen Rothwell
2008-11-14  0:01   ` Greg KH
2008-11-14  0:13     ` J.R. Mauro
2008-11-14  0:22       ` Greg KH
2008-11-14  0:25         ` J.R. Mauro
2008-11-14  7:42 ` Geert Uytterhoeven
2008-11-14  7:50   ` Stephen Rothwell
2008-11-14 14:16     ` Geert Uytterhoeven
2008-11-14 17:32   ` Greg KH [this message]
2008-11-14 22:28     ` J.R. Mauro
2008-11-14 23:06       ` Greg KH
2008-11-14 23:43         ` J.R. Mauro
2008-11-18 18:36     ` Stefan Richter

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=20081114173258.GC22980@kroah.com \
    --to=greg@kroah.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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