lkml.org 
[lkml]   [2007]   [Apr]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 0/30] Use menuconfig objects

On Apr 11 2007 07:42, Al Boldi wrote:
>Jan Engelhardt wrote:
>
>Correct, no oversight here; but it may be more meaningful, if you could
>default select child-options based on the parent-state, like HW_RANDOM.

A symbol will already have the 'magic' you describe if its creator wrote
it that way. Changing to 'menuconfig' tokens does not change that I
think. Consider:

menu "foobar"
config FOOBAR
bool "foobar"
default y

config HW_RANDOM
depends on FOOBAR
default y

endmenu

This example should do things as you describe -- if FOOBAR is changed
from n to y, HW_RANDOM should automatically do the same since it is a
new option then.

menuconfig FOOBAR
bool "foobar"
default y

if FOOBAR

config HW_RANDOM
default y

endif

inhibits the same behavior AFAICS.

>Also, I don't think it's necessary to touch any of the "depends on"; keep
>them as is, as they don't hurt staying that way, and may actually be
>necessary under certain circumstances. (see EMBEDDED)

Simplifying the depends lines is a good thing IMO.


Jan
--
-
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/

\
 
 \ /
  Last update: 2007-04-11 09:51    [W:0.064 / U:1.268 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site