netdev - Re: [PATCH 00/17] sky2 update for 2.6.22

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]

Message-ID: <46414B30.6050603@garzik.org>
Date:	Wed, 09 May 2007 00:16:48 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Stephen Hemminger <shemminger@...ux-foundation.org>
CC:	netdev@...r.kernel.org, Greg KH <greg@...ah.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 00/17] sky2 update for 2.6.22

Stephen Hemminger wrote:
> Patches are against netdev-2.6 upstream code branch.
> 
> This includes a several bug fixes, and code cleanup to use standard
> functions. There are a couple of PCI changes. One bug fix, and moving
> common code in PCI base.

The standard development process is:

	* new code gets pushed to me during 2.6.X-rc
	* that code is auto-propagated to akpm's -mm tree for
	  additional exposure
	* merge window opens
	* I push upstream

That ensures code gets at least /some/ additional review, testing, 
"settling" time.

This is a late date to be expecting stuff to be pushed straight into 2.6.22.

Additionally, the rule for creating patches is:  diff against latest 
vanilla linux-2.6.git tree, unless dependencies exist in netdev.  After 
the merge window opens, #upstream is often empty or even a bit behind 
upstream, since Linus pulls that.

	Jeff

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html