From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: linux-next: the purge :-)
Date: Wed, 7 May 2008 21:27:53 -0700 [thread overview]
Message-ID: <20080508042753.GA6876@kroah.com> (raw)
In-Reply-To: <20080508112130.fd574b50.sfr@canb.auug.org.au>
On Thu, May 08, 2008 at 11:21:30AM +1000, Stephen Rothwell wrote:
> Greg, you might consider setting up a subset (currently probably
> empty) of the ldp tree for drivers that are readier for integration.
Ok, fair enough, I totally understand.
I've now moved my trees around a bit, and would like it if you could
include the following, in this order (the # NEXT_BASE variable is set in
them to make sure things get ordered properly.)
driver-core.next
usb.next
driver-core
usb
ldp.next
The ".next" trees are what is going to Linus before the next major
release happens (bugfixes and new device ids at this point in time for
example.) The other trees are what is going to go to Linus after the
next major kernel is out.
I also have a "ldp" tree as well, but I understand why you do not want
to pull it at this time into linux-next.
And, there is a real driver already in the ldp.next tree that should
show up in 2.6.27, so it isn't empty at this time :)
If you have any questions about these trees, please let me know.
thanks,
greg k-h
next prev parent reply other threads:[~2008-05-08 4:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 1:21 linux-next: the purge :-) Stephen Rothwell
2008-05-08 1:56 ` John W. Linville
2008-05-08 4:33 ` Stephen Rothwell
2008-05-08 4:27 ` Greg KH [this message]
2008-05-08 6:27 ` Adrian Bunk
2008-05-08 22:04 ` Greg KH
2008-05-09 1:16 ` Stephen Rothwell
2008-05-09 3:44 ` Greg KH
2008-05-09 4:18 ` Greg KH
2008-05-09 6:10 ` Stephen Rothwell
2008-05-08 9:55 ` Thomas Gleixner
2008-05-08 10:46 ` 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=20080508042753.GA6876@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.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