linux-kernel - Re: Announce: Linux-next (Or Andrew's dream :-))

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: <47B1EA0E.7080602@garzik.org>
Date:	Tue, 12 Feb 2008 13:48:46 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	Greg KH <greg@...ah.com>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	David Miller <davem@...emloft.net>, arjan@...radead.org,
	sfr@...b.auug.org.au, linux-kernel@...r.kernel.org,
	linux-next@...r.kernel.org, linux-arch@...r.kernel.org,
	akpm@...ux-foundation.org
Subject: Re: Announce: Linux-next (Or Andrew's dream :-))

Greg KH wrote:
> A lot of time that already happens today, between the different
> subsystem maintainers.  We routinely pass PCI and driver core changes
> through the network and scsi and ata trees in order to handle merge
> issues properly.  This already happened in a few places in the
> 2.6.25-rc1 merge cycle.

Yep.  I do that with the powerpc tree sometimes, too:  I'll ACK a 
drivers/net change that is obviously PPC-specific, and that drivers/net 
change will go in via paulus.

Like you said, it's done on a per-patch not git tree basis at the moment.

That sort of cooperation has become common: in areas of shared 
responsibility, request an ack, and then the "most obvious" person 
(generally the one with most merge dependencies) merges that 
shared-responsibility change along with some other changes specific to 
their own tree.

	Jeff

--
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/