From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751290AbZALJcv (ORCPT ); Mon, 12 Jan 2009 04:32:51 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751788AbZALJcm (ORCPT ); Mon, 12 Jan 2009 04:32:42 -0500 Received: from mx2.mail.elte.hu ([157.181.151.9]:44379 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751462AbZALJcl (ORCPT ); Mon, 12 Jan 2009 04:32:41 -0500 Date: Mon, 12 Jan 2009 10:32:14 +0100 From: Ingo Molnar To: Stephen Rothwell Cc: Benjamin Herrenschmidt , Linus Torvalds , linux-next@vger.kernel.org, Rusty Russell , Mike Travis , Andrew Morton , "David S. Miller" , LKML , Paul Mackerras , linuxppc-dev@ozlabs.org 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 Content-Disposition: inline In-Reply-To: <20090112202427.3b918490.sfr@canb.auug.org.au> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: 1.0 X-ELTE-SpamLevel: s X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=1.0 required=5.9 tests=BAYES_50 autolearn=no SpamAssassin version=3.2.3 1.0 BAYES_50 BODY: Bayesian spam probability is 40 to 60% [score: 0.4956] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * 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