From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.mail.elte.hu (mx2.mail.elte.hu [157.181.151.9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 88AF947534 for ; Mon, 12 Jan 2009 20:32:36 +1100 (EST) Date: Mon, 12 Jan 2009 10:32:14 +0100 From: Ingo Molnar To: Stephen Rothwell Subject: Re: linux-next: origin tree build failure Message-ID: <20090112093214.GA6798@elte.hu> References: <20090112104837.69feedec.sfr@canb.auug.org.au> <1231719015.22571.4.camel@pasglop> <20090112090552.GD26750@elte.hu> <20090112202427.3b918490.sfr@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20090112202427.3b918490.sfr@canb.auug.org.au> Cc: Rusty Russell , LKML , Mike Travis , linuxppc-dev@ozlabs.org, linux-next@vger.kernel.org, Paul Mackerras , Andrew Morton , Linus Torvalds , "David S. Miller" List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , * Stephen Rothwell wrote: > > It slipped through because it didnt get caught in build tests because > > cpufreq isnt enabled in the powerpc defconfig. > > Which is one of the reasons we have linux-next: "integration testing". Build bugs slipped through that net too in the past. And we dont really want developers and maintainers to rely on an external middle man facility to be able to submit patches. So the best method is to make the defconfigs good enough to catch everyday build bugs. Random testing and linux-next can then catch the weird special cases as well. Ingo