Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934458AbZIDW6r (ORCPT ); Fri, 4 Sep 2009 18:58:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S934445AbZIDW6r (ORCPT ); Fri, 4 Sep 2009 18:58:47 -0400 Received: from terminus.zytor.com ([198.137.202.10]:36510 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934420AbZIDW6q (ORCPT ); Fri, 4 Sep 2009 18:58:46 -0400 Message-ID: <4AA19AAE.9050909@zytor.com> Date: Fri, 04 Sep 2009 15:54:38 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1) Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Thunderbird/3.0b3 MIME-Version: 1.0 To: David Woodhouse CC: Randy Dunlap , Ingo Molnar , linux-kernel@vger.kernel.org, mingo@redhat.com, sam@ravnborg.org, tglx@linutronix.de, linux-tip-commits@vger.kernel.org Subject: Re: [tip:x86/kbuild] x86: Don't silently override CONFIG_64BIT in 'make oldconfig' References: <20090904144857.GA12872@elte.hu> <4AA13FE6.20807@zytor.com> <20090904093846.a87bd198.randy.dunlap@oracle.com> <1252100456.4483.544.camel@macbook.infradead.org> In-Reply-To: <1252100456.4483.544.camel@macbook.infradead.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 699 Lines: 20 On 09/04/2009 02:40 PM, David Woodhouse wrote: > On Fri, 2009-09-04 at 09:38 -0700, Randy Dunlap wrote: >> >> what does ARCH=x86 mean? > > A bit like ARCH=powerpc. It's the new combined architecture where 64-bit > vs. 32-bit is just a config choice. ARCH=i386 and ARCH=x86_64 are just > historical baggage, and should be dropped like ARCH=ppc and ARCH=ppc64 > were. > >From a cursory look it looks like ARCH=powerpc won't work for UM, either. -hpa -- 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/