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: Wed, 14 Mar 2007 09:49:08 -0700 (PDT) From: Linus Torvalds <torvalds@...ux-foundation.org> To: Ingo Molnar <mingo@...e.hu> cc: Steven Rostedt <rostedt@...dmis.org>, Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>, Chris Wright <chrisw@...s-sol.org>, Rusty Russell <rusty@...tcorp.com.au>, Glauber de Oliveira Costa <glommer@...il.com> Subject: Re: [PATCH 00/18] Make common x86 arch area for i386 and x86_64 - Take 2 On Wed, 14 Mar 2007, Ingo Molnar wrote: > > symbolic links perhaps? In that case i'd also introduce a common naming > scheme: x86_early_printk.c - to make sure we know it right away that > those files are bi-arch. Hey, I know! This is a radical idea, but what if we put the name at the head of the file, and called it arch/x86/kernel/early_printk.c instead? Then we could teach each of i386 and x86-64 to include it from that area, and we could put other shared files under the same directory hierarchy so that it would be easy to see which ones are shared? Crazy idea, I know. But I think I saw somebody send out a patch kind of like that, so maybe this common naming scheme could be as simple as just applying a few patches once they got cleaned up and re-organized some more. Linus - 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