Re: [RFC] Rename various 'IA32' uses in arch/x86/ code
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [RFC] Rename various 'IA32' uses in arch/x86/ code
- From: Ingo Molnar <mingo@xxxxxxxxxx>
- Date: Sun, 21 Jun 2015 15:44:00 +0200
- Cc: Brian Gerst <brgerst@xxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Peter Zijlstra <peterz@xxxxxxxxxxxxx>, Borislav Petkov <bp@xxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, Denys Vlasenko <dvlasenk@xxxxxxxxxx>, Andy Lutomirski <luto@xxxxxxxxxxxxxx>, linux-tip-commits@xxxxxxxxxxxxxxx
- In-reply-to: <CBABD26C-3354-4FEE-A24F-01499F5F0C29@zytor.com>
- User-agent: Mutt/1.5.23 (2014-03-12)
* H. Peter Anvin <hpa@xxxxxxxxx> 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-tip-commits" in
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]