summaryrefslogtreecommitdiffstats
path: root/virt/kvm
diff options
context:
space:
mode:
authorArnaud Lacombe <lacombar@gmail.com>2012-01-23 17:29:05 -0500
committerMichal Marek <mmarek@suse.cz>2012-01-26 11:01:56 +0100
commit5d09598d488f081e3be23f885ed65cbbe2d073b5 (patch)
tree077850c02c72b29a8b5b1f5fa95a1cf2adae5275 /virt/kvm
parentdcd6c92267155e70a94b3927bce681ce74b80d1f (diff)
downloadlinux-5d09598d488f081e3be23f885ed65cbbe2d073b5.tar.gz
linux-5d09598d488f081e3be23f885ed65cbbe2d073b5.tar.bz2
linux-5d09598d488f081e3be23f885ed65cbbe2d073b5.zip
kconfig: fix new choices being skipped upon config update
Running `oldconfig' after any of the following configuration change: either trivial addition, such as: config A bool "A" choice prompt "Choice ?" depends on A config CHOICE_B bool "Choice B" config CHOICE_C bool "Choice C" endchoice or more tricky change: OLD KCONFIG | NEW KCONFIG | | config A | bool "A" | choice | choice prompt "Choice ?" | prompt "Choice ?" | config CHOICE_C | config CHOICE_C bool "Choice C" | bool "Choice C" | config CHOICE_D | config CHOICE_D bool "Choice D" | bool "Choice D" endchoice | | config CHOICE_E | bool "Choice E" | depends on A | endchoice will not cause the choice to be considered as NEW, and thus not be asked. The cause of this behavior is that choice's novelty are computed statically right after the saved configuration has been read. At this point, the new dependency's value is still unknown and asserted to be `no'. Moreover, no update to this decision is made afterward. Correct this by dynamically evaluating a choice's novelty, and removing the static evaluation. Reported-and-tested-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by: Arnaud Lacombe <lacombar@gmail.com> Signed-off-by: Michal Marek <mmarek@suse.cz>
Diffstat (limited to 'virt/kvm')
0 files changed, 0 insertions, 0 deletions