| 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: <1343241718.7045.3.camel@joe2Laptop> Date: Wed, 25 Jul 2012 11:41:58 -0700 From: Joe Perches <joe@...ches.com> To: "Luck, Tony" <tony.luck@...el.com> Cc: "Wu, Fengguang" <fengguang.wu@...el.com>, "linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>, "alsa-devel@...a-project.org" <alsa-devel@...a-project.org> Subject: RE: [PATCH] ia64: rename platform_* to ia64_platform_* On Wed, 2012-07-25 at 18:37 +0000, Luck, Tony wrote: > >> Is platform_name particularly special? > > Yes. It is the symbol that is currently colliding with other subsystem namespace. > > >> Perhaps it's be better to rename all the other > >> platform_<foo> uses to ia64_platform_<foo> > > > > That's good point in general, oh well I just wanted to make the minimal change.. > > Following that logic there isn't anything special about symbols starting with > "platform" ... and we should hunt down every global symbol in every architecture > that is local to the architecture and replace it with $arch_$symbol. > > I think I'll just take the minimal patch to fix "platform_name" and continue to > use a "fix as problems occur" algorithm to the namespace pollution problem. That can lead to a lot of naming inconsistencies. -- 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