From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753208Ab1G3Wet (ORCPT ); Sat, 30 Jul 2011 18:34:49 -0400 Received: from casper.infradead.org ([85.118.1.10]:53848 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753118Ab1G3Wea (ORCPT ); Sat, 30 Jul 2011 18:34:30 -0400 Subject: Re: [PATCH v3] x86, kconfig: Default to ARCH=x86 to avoid overriding CONFIG_64BIT From: David Woodhouse To: Arnaud Lacombe Cc: "H. Peter Anvin" , Michal Marek , "Ted Ts'o" , Ingo Molnar , x86@kernel.org, linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org Date: Sat, 30 Jul 2011 23:34:17 +0100 In-Reply-To: References: <1306707270.2029.377.camel@i7.infradead.org> <20110530104231.GF17821@elte.hu> <20110530104656.GA19532@elte.hu> <20110530105809.GA20133@elte.hu> <1A4DB87D-9B32-44C0-B7C9-47A003CABD96@mit.edu> <20110530195545.GG2890@dhcp-172-31-194-241.cam.corp.google.com> <1306795186.2029.459.camel@i7.infradead.org> <1306856937.27477.3.camel@i7.infradead.org> <4E0495F4.7080300@suse.cz> <1311986969.20983.52.camel@i7.infradead.org> <4E34548F.9040909@zytor.com> <4E347FC4.60600@zytor.com> <1312064244.22074.21.camel@i7.infradead.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.0.2 (3.0.2-3.fc15) Content-Transfer-Encoding: 7bit Message-ID: <1312065261.22074.29.camel@i7.infradead.org> Mime-Version: 1.0 X-SRS-Rewrite: SMTP reverse-path rewritten from by casper.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 2011-07-30 at 18:24 -0400, Arnaud Lacombe wrote: > How do you plan to handle x32, if it ever makes it to mainline ? I was pondering that. Surely it would involve porting the kernel itself to x32? And there's never going to be any motivation for that *other* than UML, so I can't really see it happening. What does 'uname -m' give under x32, anyway? -- dwmw2