linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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/

  reply	other threads:[~2015-06-21 13:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tip-bace7117d3fb59a6ed7ea1aa6c8994df6a28a72a@git.kernel.org>
2015-06-16 20:22 ` [tip:x86/asm] x86/asm/entry: (Re-) rename __NR_entry_INT80_compat_max to __NR_syscall_compat_max H. Peter Anvin
2015-06-18 16:49   ` [RFC] Rename various 'IA32' uses in arch/x86/ code Ingo Molnar
2015-06-18 17:49     ` Brian Gerst
2015-06-18 19:37       ` H. Peter Anvin
2015-06-19  7:13         ` Ingo Molnar
2015-06-19 17:19           ` H. Peter Anvin
2015-06-21 13:44             ` Ingo Molnar [this message]
     [not found]       ` <CA+55aFzKOyZ4ZA6zFvCNqqqkYT8hLQOXAgJRj-k+LRqvQ1iiyQ@mail.gmail.com>
2015-06-18 19:41         ` H. Peter Anvin
2015-06-18 21:13       ` Ingo Molnar
2015-06-18 22:11         ` Brian Gerst
2015-06-19  7:08           ` Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150621134400.GA22604@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=dvlasenk@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).