Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757086AbZKWXpP (ORCPT ); Mon, 23 Nov 2009 18:45:15 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756374AbZKWXpO (ORCPT ); Mon, 23 Nov 2009 18:45:14 -0500 Received: from rcsinet12.oracle.com ([148.87.113.124]:46970 "EHLO rgminet12.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755852AbZKWXpM (ORCPT ); Mon, 23 Nov 2009 18:45:12 -0500 Message-ID: <4B0B1E67.8000207@oracle.com> Date: Mon, 23 Nov 2009 15:44:39 -0800 From: Randy Dunlap Organization: Oracle Linux Engineering User-Agent: Thunderbird 2.0.0.22 (X11/20090605) MIME-Version: 1.0 To: Greg KH CC: Stephen Rothwell , Rusty Russell , gregkh@suse.de, linux-next@vger.kernel.org, LKML Subject: Re: linux-next: Tree for November 23 References: <20091123185232.1423c56b.sfr@canb.auug.org.au> <20091123111510.9b0c0714.randy.dunlap@oracle.com> <200911240924.54675.rusty@rustcorp.com.au> <4B0B1507.4060202@oracle.com> <20091124103641.abd7bd6b.sfr@canb.auug.org.au> <4B0B1CCA.7070500@oracle.com> <20091123234300.GA13647@kroah.com> In-Reply-To: <20091123234300.GA13647@kroah.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Source-IP: acsmt357.oracle.com [141.146.40.157] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090207.4B0B1E82.00C4:SCFMA4539814,ss=1,fgs=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1398 Lines: 37 Greg KH wrote: > On Mon, Nov 23, 2009 at 03:37:46PM -0800, Randy Dunlap wrote: >> Stephen Rothwell wrote: >>> Hi Randy, >>> >>> On Mon, 23 Nov 2009 15:04:39 -0800 Randy Dunlap wrote: >>>> I decided to check on linux-next (only checked x86_64 allmodconfig), >>>> and viola: >>>> >>>> CONFIG_STAGING=y >>>> CONFIG_STAGING_EXCLUDE_BUILD=y >>>> >>>> That is just too helpful. :( >>> The Kconfig was deliberately done so that the all{no,yes,mod}config >>> builds don't build the staging stuff. You need to explictly ask for it. >>> Otherwise I would spend all my time reporting/fixing errors and warnings >>> in linux-next. >>> >> no, you should just drop it after one build error. > > No. We've been through this before a while ago. We want the staging > tree in linux-next to deal with merge issues and to help the developers > who are contributing to it. > > If you want to take it out of your automated randconfig builds because > it causes you lots of problems, that's fine with me. Sure, but that's ignoring the real problem that fixes don't get merged frequently enough, even when they are known & posted. -- ~Randy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/