Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754195AbbFUNoQ (ORCPT ); Sun, 21 Jun 2015 09:44:16 -0400 Received: from mail-wi0-f177.google.com ([209.85.212.177]:36026 "EHLO mail-wi0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752070AbbFUNoG (ORCPT ); Sun, 21 Jun 2015 09:44:06 -0400 Date: Sun, 21 Jun 2015 15:44:00 +0200 From: Ingo Molnar To: "H. Peter Anvin" Cc: Brian Gerst , Linux Kernel Mailing List , Peter Zijlstra , Borislav Petkov , Thomas Gleixner , Andrew Morton , Linus Torvalds , Denys Vlasenko , Andy Lutomirski , linux-tip-commits@vger.kernel.org Subject: Re: [RFC] Rename various 'IA32' uses in arch/x86/ code Message-ID: <20150621134400.GA22604@gmail.com> References: <55808579.4050004@zytor.com> <20150618164912.GA8557@gmail.com> <9E143C8F-1F0D-4528-B354-30BB68CCBC0E@zytor.com> <20150619071305.GB14768@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 766 Lines: 28 * H. Peter Anvin 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/