Re: [PATCH 13/30] Use menuconfig objects - IEEE1394

[Jan Engelhardt]

On Apr 28 2007 12:41, Stefan Richter wrote:
>
>So, shall I put Jan's patch aside until there is only one stack left?

Sort of.

>Or what about:
>
>	menuconfig FIREWIRE_SUPPORT
>		tristate "IEEE 1394 (FireWire) support"
>
>	config FIREWIRE
>		tristate "new FireWire stack, alias Juju"
>		depends on FIREWIRE_SUPPORT && !(IEEE1394=y)
>		default m
>	[...]
>
>	config IEEE1394
>		tristate "legacy FireWire stack"
>		depends on FIREWIRE_SUPPORT && !(FIREWIRE=y)

Would
&& FIREWIRE != y
work?

>		default m
>	[...]
>
>	comment "You can have both stacks installed but should blacklist
>	         the modules of one of them.  Else modules from both
>	         stacks will be autoloaded on hotplug events."
>		depends on FIREWIRE && IEEE1394

If you *really* want to do that, then have it. But when a menu has
two or three choices (in this case: larger subsystems), it's rand()
for me whether or not to convert to menuconfig.
Feel free.



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