linux-kernel - Re: linux-next: the purge :-)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 7 May 2008 21:27:53 -0700
From:	Greg KH <greg@...ah.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org,
	"John W. Linville" <linville@...driver.com>,
	Ingo Molnar <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Sam Ravnborg <sam@...nborg.org>
Subject: Re: linux-next: the purge :-)

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/