On Fri, 19 Oct 2007 18:22:45 -0700 David Brownell wrote:

quoted text
> 	(Originally posted to kbuild-devel per MAINTAINERS, but
> 	that post was rejected since that is -- undocumented,
> 	sigh -- a members-only list.)

That mailing list is no longer used.  Today's git pull for kbuild
included this change:

 KCONFIG
 P:	Roman Zippel
 M:	zippel@linux-m68k.org
-L:	kbuild-devel@lists.sourceforge.net
+L:	linux-kbuild@vger.kernel.org
 S:	Maintained


quoted text
> Hi,
> 
> I noticed a regression, visible in the drivers/usb/gadget Kconfig;
> it seems to be quite recent.
> 
> That Kconfig hasn't changed (other than adding new drivers), and
> it's worked that way for several years now ... so the issue seems
> to be changes in menuconfig/kconfig/etc semantics.
> 
> The issue is that when USB_GADGET=m, it's no longer possible to
> configure peripheral controller drivers as modules ... the controller
> drivers can now only be configured for static linkage.
> 
> It should be making a choice of one of the controller drivers which
> could work on the target system, and allow that driver to be linked
> either as a module (ok iff USB_GADGET=m) or statically.
> 
> What's the deal here?

Hm, it does look very odd.  It looks like it has something to
do with <choice> working differently for some reason.

In xconfig, I set all of the View Options and when I click on one
of the periph. controllers, it says

	depends on =y && PCI

but if I back up to -git7, it says

	depends on <choice> && PCI

I'll keep looking.

---
~Randy
-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/