From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.lixom.net (lixom.net [66.141.50.11]) by ozlabs.org (Postfix) with ESMTP id 66D1167B9B for ; Thu, 30 Nov 2006 05:47:15 +1100 (EST) Date: Wed, 29 Nov 2006 12:45:11 -0600 From: Olof Johansson To: linas@austin.ibm.com (Linas Vepstas) Subject: Re: [PATCH] ppc64_defconfig to use AUTOFS_V4 not V3 Message-ID: <20061129124511.3be6b9a8@localhost.localdomain> In-Reply-To: <20061129180522.GM10879@austin.ibm.com> References: <20061129180522.GM10879@austin.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: linuxppc-dev@ozlabs.org, nfonteno@us.ibm.com, Paul Mackerras List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 29 Nov 2006 12:05:22 -0600 linas@austin.ibm.com (Linas Vepstas) wrote: > Please apply. Although I have a general question: who is served > by the ppc64_defconfig these days? Any reason why its not more > like powerpc_defcofig? "make defconfig" uses uname -m to pick up > the defconfig, and my cell, rhel5 and sles10 boxes report ppc64 > not pseries for uname -m. I like using it to build a kernel that runs on as much as possible with a single image, but I don't think all platforms have been added there (yet). Sort of like a superset of all other 64-bit configs. -Olof