From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756126Ab1HSUdu (ORCPT ); Fri, 19 Aug 2011 16:33:50 -0400 Received: from oproxy5-pub.bluehost.com ([67.222.38.55]:43242 "HELO oproxy5-pub.bluehost.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1753368Ab1HSUdr (ORCPT ); Fri, 19 Aug 2011 16:33:47 -0400 Date: Fri, 19 Aug 2011 13:33:45 -0700 From: Randy Dunlap To: Stephen Rothwell Cc: "Pihet-XID, Jean" , "Rafael J. Wysocki" , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: linux-next: build failure after merge of the final tree (pm tree related) Message-Id: <20110819133345.36349fc9.rdunlap@xenotime.net> In-Reply-To: <20110819233950.e526ac71ca862f45538b8721@canb.auug.org.au> References: <20110819130328.ee5c4b7191db0ce2c8a02e39@canb.auug.org.au> <20110819233950.e526ac71ca862f45538b8721@canb.auug.org.au> Organization: YPO4 X-Mailer: Sylpheed 2.7.1 (GTK+ 2.16.6; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Identified-User: {1807:box742.bluehost.com:xenotime:xenotime.net} {sentby:smtp auth 50.53.38.135 authed with rdunlap@xenotime.net} Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 19 Aug 2011 23:39:50 +1000 Stephen Rothwell wrote: > Hi, > > On Fri, 19 Aug 2011 10:14:11 +0200 "Pihet-XID, Jean" wrote: > > > > Well, it is not as easy as it seems. As the patch set describes, I am > > build testing for x86 and OMAP. At the moment due to config > > dependencies it is _impossible_ to disable PM in the OMAP config. > > > > Also I cannot build test every platform out there. > > Do you have a procedure for build testing? > > I do not expect developers (or even maintainers) to build for every > architecture/platform - that is partly what linux-next is for (see > http://kisskb.ellerman.id.au/linux-next ). It is good to see you at > least thought about the !PM case. Can't it be turned off in x86? Sure it can. For mainline -rc and 3.x releases, I am trying to build an almost-allmodconfig kernel (x86_64 only) with one major option disabled. The $major option that is disabled is one of each of the following: BLOCK HOTPLUG INET INPUT MAGIC_SYSRQ NET PCI PM PROC_FS SMP SYSCTL SYSFS There used to be several build errors for HOTPLUG or MAGIC_SYSRQ disabled, but those aren't finding problems lately like they used to. I could probably drop them. > I am a bit sensitive about these sort of build errors as I see it happen > way to often that a developer make a typo in the !CONFIG_XXX stubs. --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code ***