From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from e8.ny.us.ibm.com (e8.ny.us.ibm.com [32.97.182.138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "e8.ny.us.ibm.com", Issuer "GeoTrust SSL CA" (not verified)) by ozlabs.org (Postfix) with ESMTPS id 5EE132C0082 for ; Fri, 14 Sep 2012 04:04:00 +1000 (EST) Received: from /spool/local by e8.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 13 Sep 2012 14:03:56 -0400 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay01.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q8DI3sL0024586 for ; Thu, 13 Sep 2012 14:03:54 -0400 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q8DI3rMe011613 for ; Thu, 13 Sep 2012 15:03:54 -0300 Date: Thu, 13 Sep 2012 11:03:40 -0700 From: Nishanth Aravamudan To: Stephen Rothwell Subject: Re: [PATCH] pseries: double NR_CPUS in defconfig Message-ID: <20120913180340.GH9269@linux.vnet.ibm.com> References: <20120912174706.GE9269@linux.vnet.ibm.com> <20120913223739.48f27d7fbacca32b013777fc@canb.auug.org.au> <20120913180011.GG9269@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20120913180011.GG9269@linux.vnet.ibm.com> Cc: linuxppc-dev@lists.ozlabs.org, Anton Blanchard , Paul Mackerras List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 13.09.2012 [11:00:11 -0700], Nishanth Aravamudan wrote: > Hi Stephen, > > On 13.09.2012 [22:37:39 +1000], Stephen Rothwell wrote: > > Hi, > > > > On Wed, 12 Sep 2012 10:47:07 -0700 Nishanth Aravamudan wrote: > > > > > > Anticipating growth in coming years, we should ensure we are getting > > > a good lead on testing. > > > > Most changes to pseries_defconfig are copied into ppc64_defconfig. > > Should this one be as well? > > Ah, I didn't realize that was the case, sorry. Yes, it probably does > make sense to do this change. Should I just send a follow-on patch? Actually, ppc64_defconfig doesn't currently define CONFIG_NR_CPUS. NR_CPUS' powerpc Kconfig allows 2-8192 already, so given the current state, I'm not sure any further patch is necessary? Thanks, Nish