From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:53930 "EHLO sunset.davemloft.net" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1752244AbYBMIyC (ORCPT ); Wed, 13 Feb 2008 03:54:02 -0500 Date: Wed, 13 Feb 2008 00:54:33 -0800 (PST) Message-Id: <20080213.005433.23276743.davem@davemloft.net> Subject: Re: distributed module configuration From: David Miller In-Reply-To: <20080213084541.GA8091@uranus.ravnborg.org> References: <20080212191552.GA20883@kroah.com> <20080212.164149.209357519.davem@davemloft.net> <20080213084541.GA8091@uranus.ravnborg.org> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-arch-owner@vger.kernel.org List-ID: To: sam@ravnborg.org Cc: greg@kroah.com, torvalds@linux-foundation.org, jeff@garzik.org, arjan@infradead.org, sfr@canb.auug.org.au, linux-kernel@vger.kernel.org, linux-next@vger.kernel.org, linux-arch@vger.kernel.org, akpm@linux-foundation.org, linux-kbuild@vger.kernel.org From: Sam Ravnborg Date: Wed, 13 Feb 2008 09:45:41 +0100 > So we could do: > > config foo > tristate "do you want foo?" > depends on USB && BAR > module > obj-$(CONFIG_FOO) += foo.o > foo-y := file1.o file2.o > help > foo will allow you to explode your PC ... > Does this fit what you had in mind? Yes it does. Now I'll ask if you think embedding this information in one of the C files for a module would be even nicer? Also, we need to make sure we can properly handle top-level container-like items. For example, where would menuconfigs like NETDEV_10000 go if we adopt this kind of scheme?