[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080213.010628.151359756.davem@davemloft.net>
Date: Wed, 13 Feb 2008 01:06:28 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: sam@...nborg.org
Cc: greg@...ah.com, torvalds@...ux-foundation.org, jeff@...zik.org,
arjan@...radead.org, sfr@...b.auug.org.au,
linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
linux-arch@...r.kernel.org, akpm@...ux-foundation.org,
linux-kbuild@...r.kernel.org
Subject: Re: distributed module configuration
From: Sam Ravnborg <sam@...nborg.org>
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_10000 go if we adopt this kind of scheme?
>
> If it makes sense to group stuff inside a menuconfig it would
> also make sense to put the same modules in a subdirectory.
> And then we would have the menuconfig in the Kconfig
> file that would source the others.
Sounds good to me.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists