From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750877AbWG0Am0 (ORCPT ); Wed, 26 Jul 2006 20:42:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751127AbWG0Am0 (ORCPT ); Wed, 26 Jul 2006 20:42:26 -0400 Received: from scrub.xs4all.nl ([194.109.195.176]:43748 "EHLO scrub.xs4all.nl") by vger.kernel.org with ESMTP id S1750877AbWG0Am0 (ORCPT ); Wed, 26 Jul 2006 20:42:26 -0400 Date: Thu, 27 Jul 2006 02:42:20 +0200 (CEST) From: Roman Zippel X-X-Sender: roman@scrub.home To: Dmitry Torokhov cc: linux-kernel@vger.kernel.org Subject: Re: Fwd: Using select in boolean dependents of a tristate symbol In-Reply-To: Message-ID: References: <200607132231.46776.dtor@insightbb.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Wed, 19 Jul 2006, Dmitry Torokhov wrote: > Another question for you - what is the best way to describe > dependancy of a sub-option on a subsystem so you won't end up with the > subsystem as a module and user built in. Something like > > config IBM_ASM > tristate "Device driver for IBM RSA service processor" > depends on X86 && PCI && EXPERIMENTAL > ... > config IBM_ASM_INPUT > bool "Support for remote keyboard/mouse" > depends on IBM_ASM && (INPUT=y || INPUT=IMB_ASM) > > But the above feels yucky. Could we have something like: > > depends on matching(INPUT, IBM_ASM) This is not really descriptive of what it does, is it? Linus suggested a syntax like (IBM_ASM && IMB_ASM<=INPUT) Another alternative which works now is to just disable the one invalid case explicitely: depends on IBM_ASM && INPUT depends on !(IBM_ASM=y && INPUT=m) bye, Roman