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
| ||
|
Message-ID: <20071207174843.GA20441@stusta.de> Date: Fri, 7 Dec 2007 18:48:43 +0100 From: Adrian Bunk <bunk@...nel.org> To: Tejun Heo <htejun@...il.com> Cc: sam@...nborg.org, Linux Kernel <linux-kernel@...r.kernel.org>, notting@...hat.com, rusty@...tcorp.com.au, kay.sievers@...y.org, greg@...ah.com Subject: Re: [PATCH] kbuild: implement modules.order On Tue, Dec 04, 2007 at 10:49:37PM +0900, Tejun Heo wrote: > When multiple built-in modules (especially drivers) provide the same > capability, they're prioritized by link order specified by the order > listed in Makefile. This implicit ordering is lost for loadable > modules. >... What exactly are the drivers you are thinking of? I would rather see us getting away from any link order dependencies. E.g. we might one day want to compile the whole kernel with one gcc call (using "--combine -fwhole-program"). cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed -- 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/
Powered by blists - more mailing lists