Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261354AbUKSLTE (ORCPT ); Fri, 19 Nov 2004 06:19:04 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261350AbUKSLTE (ORCPT ); Fri, 19 Nov 2004 06:19:04 -0500 Received: from mail-ex.suse.de ([195.135.220.2]:21663 "EHLO Cantor.suse.de") by vger.kernel.org with ESMTP id S261348AbUKSLSt (ORCPT ); Fri, 19 Nov 2004 06:18:49 -0500 Date: Fri, 19 Nov 2004 12:18:47 +0100 Message-ID: From: Takashi Iwai To: Adrian Bunk Cc: ak@suse.de, Andrew Morton , Linus Torvalds , discuss@x86-64.org, linux-kernel@vger.kernel.org Subject: Re: RFC: let x86_64 no longer define X86 In-Reply-To: <20041119005117.GM4943@stusta.de> References: <20041119005117.GM4943@stusta.de> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 MULE XEmacs/21.4 (patch 15) (Security Through Obscurity) (i386-suse-linux) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 841 Lines: 29 At Fri, 19 Nov 2004 01:51:17 +0100, Adrian Bunk wrote: > > I'd like to send a patch after 2.6.10 that removes the following from > arch/x86_64/Kconfig: > > config X86 > bool > default y > > Additionally, I'll also check all current X86 uses to prevent breakages. > > > Why? > > X86 is _the_ symbol to identify the i386 architecture, but the x86_64 > port hijacked it. Kernel-wise, x86_64 is mostly simply a new port like > e.g. ia64. If we do this for x86-64, shouldn't we do the same for ppc64 and sh64, too? (only sparc64 seems not defining 32bit config.) Takashi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/