From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761130AbXKDCCr (ORCPT ); Sat, 3 Nov 2007 22:02:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755894AbXKDCCi (ORCPT ); Sat, 3 Nov 2007 22:02:38 -0400 Received: from srv5.dvmed.net ([207.36.208.214]:52465 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754197AbXKDCCi (ORCPT ); Sat, 3 Nov 2007 22:02:38 -0400 Message-ID: <472D282B.2000208@garzik.org> Date: Sat, 03 Nov 2007 22:02:19 -0400 From: Jeff Garzik User-Agent: Thunderbird 2.0.0.5 (X11/20070727) MIME-Version: 1.0 To: Sam Ravnborg CC: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , LKML , Andrew Morton Subject: Re: [PATCH] replace "make ARCH=i386/x86_64 with make ARCH=x86" References: <20071103234826.GA26654@uranus.ravnborg.org> In-Reply-To: <20071103234826.GA26654@uranus.ravnborg.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.4 (----) X-Spam-Report: SpamAssassin version 3.1.9 on srv5.dvmed.net summary: Content analysis details: (-4.4 points, 5.0 required) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Sam Ravnborg wrote: > This patchset unify the i386 and x86_64 Kconfig > files for x86. > In addition it replaces the use of ARCH=i386 and > ARCH=x86_64 with the more intuitive ARCH=x86. > > The primary purpose of this patch serie is to > enable make ARCH=x86 and let the config decide > if we are building for 32 or 64 bit. Yuck, I dislike. Please don't take away this nice development workflow. the current workflow of make ARCH=i386 allmodconfig && make ARCH=i386 -sj5 no longer works. Now, the new and ungainly step of editing the .config is added, with vi or sed. This also opens a chicken-and-egg problem... What kind of config is generated by allmodconfig when ARCH==x86? There is no good answer. The existing tradition of switching between 32-bit and 64-bit was quite nice, and it was done in The Obvious Way(tm) -- via the method for specifying the architecture/platform. Switching to Kconfig for that decision is a step backwards in usability and IMO violates the Principle of Least Surprise. Jeff