Re: distributed module configuration

2008-02-22 Thread Pavel Machek
Hi! > > 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? I kind of like to be able to grep over just Kconfig files, to find out what is going on... -- (english) http://www.liv

Re: distributed module configuration [Was: Announce: Linux-next (Or Andrew's dream :-))]

2008-02-14 Thread Sam Ravnborg
On Thu, Feb 14, 2008 at 01:56:13AM +0100, Roman Zippel wrote: > Hi, > > On Wednesday 13. February 2008, Sam Ravnborg wrote: > > > config foo > > tristate "do you want foo?" > > depends on USB && BAR > > module > > obj-$(CONFIG_FOO) += foo.o > > foo-y := file1.o file2.o > >

Re: distributed module configuration [Was: Announce: Linux-next (Or Andrew's dream :-))]

2008-02-14 Thread Geert Uytterhoeven
On Thu, 14 Feb 2008, Roman Zippel wrote: > On Wednesday 13. February 2008, Sam Ravnborg wrote: > > 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 allo

Re: distributed module configuration [Was: Announce: Linux-next (Or Andrew's dream :-))]

2008-02-13 Thread Roman Zippel
Hi, On Wednesday 13. February 2008, Sam Ravnborg wrote: > 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 I'm more thin

Re: distributed module configuration

2008-02-13 Thread Giacomo A. Catenazzi
Sam Ravnborg wrote: On Wed, Feb 13, 2008 at 12:54:33AM -0800, David Miller wrote: From: Sam Ravnborg <[EMAIL PROTECTED]> 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

Re: distributed module configuration

2008-02-13 Thread David Miller
From: Sam Ravnborg <[EMAIL PROTECTED]> Date: Wed, 13 Feb 2008 10:04:51 +0100 > On Wed, Feb 13, 2008 at 12:54:33AM -0800, David Miller wrote: > > Also, we need to make sure we can properly handle top-level > > container-like items. For example, where would menuconfigs like > > NETDEV_1 go if w

Re: distributed module configuration

2008-02-13 Thread Sam Ravnborg
On Wed, Feb 13, 2008 at 12:54:33AM -0800, David Miller wrote: > From: Sam Ravnborg <[EMAIL PROTECTED]> > 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) += f

Re: distributed module configuration

2008-02-13 Thread David Miller
From: Sam Ravnborg <[EMAIL PROTECTED]> 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 al

distributed module configuration [Was: Announce: Linux-next (Or Andrew's dream :-))]

2008-02-13 Thread Sam Ravnborg
> > 2) Let's move away from some/dir/{Kconfig,Makefile} schemes and >instead have each "thing" have it's own Kconfig.foo or >Makefile.foo that gets automatically sucked into the main >directory Makefile or Kconfig using file globs or similar. So we could do: config foo trista