| 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: <20070910192920.GA2080@elte.hu> Date: Mon, 10 Sep 2007 21:29:20 +0200 From: Ingo Molnar <mingo@...e.hu> To: Thomas Gleixner <tglx@...utronix.de> Cc: Sam Ravnborg <sam@...nborg.org>, Andi Kleen <ak@...e.de>, LKML <linux-kernel@...r.kernel.org>, kbuild devel <kbuild-devel@...ts.sourceforge.net> Subject: Re: [RFC] kbuild - introduce vdir to make life easier for x86_64 * Thomas Gleixner <tglx@...utronix.de> wrote: > On Mon, 2007-09-10 at 21:11 +0200, Sam Ravnborg wrote: > > One of the complaints raised about the current x86_64 Makfiles are > > the ugliness needed to reuse code from i386. Andi asked me if we > > could do something in kbuild to make this less ugly and below are > > the hack I could come up with. > > while in general this is definitely a nice change, it does not really > solve the real problem of code scattered across two architectures. The > Makefile polishing is the least thing we care about. > > Thanks, i'd like to add it here that Makefile polishing is important - it's just that in the context of arch/*x86* the Makefile impact of the current cross-arch code sharing practice is one of the smaller problems and the Makefiles get cleaned up via the arch/x86 merge anyway. Ingo - 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