Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261619AbUKSWfx (ORCPT ); Fri, 19 Nov 2004 17:35:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261677AbUKSWeg (ORCPT ); Fri, 19 Nov 2004 17:34:36 -0500 Received: from ozlabs.org ([203.10.76.45]:49031 "EHLO ozlabs.org") by vger.kernel.org with ESMTP id S261667AbUKSWa7 (ORCPT ); Fri, 19 Nov 2004 17:30:59 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16798.29733.364848.474665@cargo.ozlabs.ibm.com> Date: Sat, 20 Nov 2004 09:31:01 +1100 From: Paul Mackerras To: Takashi Iwai Cc: Adrian Bunk , 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: References: <20041119005117.GM4943@stusta.de> X-Mailer: VM 7.19 under Emacs 21.3.1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 451 Lines: 13 Takashi Iwai writes: > 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.) Both ppc32 and ppc64 define CONFIG_PPC already. Paul. - 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/