Re: [RFC] Rename various 'IA32' uses in arch/x86/ code

From: Ingo Molnar <mingo@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Brian Gerst <brgerst@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Borislav Petkov <bp@alien8.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Denys Vlasenko <dvlasenk@redhat.com>,
	Andy Lutomirski <luto@amacapital.net>,
	linux-tip-commits@vger.kernel.org
Subject: Re: [RFC] Rename various 'IA32' uses in arch/x86/ code
Date: Sun, 21 Jun 2015 15:44:00 +0200	[thread overview]
Message-ID: <20150621134400.GA22604@gmail.com> (raw)
In-Reply-To: <CBABD26C-3354-4FEE-A24F-01499F5F0C29@zytor.com>

* H. Peter Anvin <hpa@zytor.com> wrote:

> x86-32 is clumsy though.  "Original name that stuck" is perfectly legitimate, 
> and having multiple names for the same thing is always worse then having 
> slightly imperfect names.

But at least for Kconfigs X86-32 is the name that is much more common:

 triton:~/tip> make ARCH=i386 allmodconfig
 triton:~/tip> grep _386 .config
 triton:~/tip> grep _X86_32 .config
 CONFIG_X86_32=y
 CONFIG_X86_32_SMP=y
 CONFIG_X86_32_LAZY_GS=y
 CONFIG_X86_32_NON_STANDARD=y
 CONFIG_X86_32_IRIS=m

So I'd go with that.

Also, since we have 'x86-64', not Not sure I'd consider 'x86-32' clumsy.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at  http://www.tux.org/lkml/