| 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
| ||
|
Date: Tue, 25 Aug 2009 15:35:42 +0100 From: "Jan Beulich" <JBeulich@...ell.com> To: "Ingo Molnar" <mingo@...e.hu> Cc: <tglx@...utronix.de>, <mingo@...hat.com>, <linux-kernel@...r.kernel.org>, <linux-tip-commits@...r.kernel.org>, <hpa@...or.com> Subject: Re: [tip:x86/urgent] x86: Fix build with older binutilsandconsolidate linker script >>> Ingo Molnar <mingo@...e.hu> 25.08.09 16:14 >>> > >* Jan Beulich <JBeulich@...ell.com> wrote: > >> >>> Ingo Molnar <mingo@...e.hu> 25.08.09 15:56 >>> >> >Would it be possible to split it into two pieces: 'minimal fix' and >> >'clean up' portions? >> >> Besides being cumbersome, that would make it even larger, so I'd >> say that's not worth it. > >I mean the two patches yield the same end result. The first one I also understood it that way. >(which is smaller, hopefully) gets committed to x86/urgent, the >second one (the cleanups and other non-essentials) gets pushed >upstream in .32. The cleanup part really isn't much more than what I described with "Once touching this code, also use the various data section helper macros from include/asm-generic/vmlinux.lds.h.", and if the first patch wouldn't use those macros, it would just grow and become even less readable. Jan -- 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