From mboxrd@z Thu Jan 1 00:00:00 1970 From: Len Brown Subject: Re: on builds/randconfigs (was: [PATCH -next] thermal: depends on NET) Date: Wed, 12 Jan 2011 16:58:26 -0500 (EST) Message-ID: References: <20101213163607.0b0a7c3a.sfr@canb.auug.org.au> <20110112131800.d64c1a86.akpm@linux-foundation.org> <201101122224.54330.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: Received: from vms173019pub.verizon.net ([206.46.173.19]:62299 "EHLO vms173019pub.verizon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756510Ab1ALV6q (ORCPT ); Wed, 12 Jan 2011 16:58:46 -0500 In-reply-to: <201101122224.54330.rjw@sisk.pl> Sender: linux-next-owner@vger.kernel.org List-ID: To: "Rafael J. Wysocki" Cc: Andrew Morton , Randy Dunlap , linux-acpi@vger.kernel.org, Stephen Rothwell , Zhang Rui , linux-next@vger.kernel.org, LKML , Zimny Lech > > These unusable config combinations should be prevented via Kconfig. > > That prevents users from selecting them, which otherwise adds to > > our workload and to theirs. It also prevents false-positives > > during our useful randconfig testing. > > But it is kind of difficult to achieve IMhO. For example, there are options > that are only SELECTed if something else is set, but randconfig doesn't seem > to care. Kconfig select needs to be fixed so that it is not possible to select something if that something's dependencies are not met. This long standing issue is independent of randconfig, but Randy can probably attest that a measurable portion of the randconfig failures are due to this bug. -Len Brown, Intel Open Source Technology Center