Dirk Gouders <dirk@xxxxxxxxxxx> writes: [SNIP] >> Are you sure this test-case exhibits the problem for you? > > Yes, but obviously, I did not describe it very clearly. The steps to > reproduce the problem are: > > $ ./scripts/kconfig/mconf test.in > --> change c0 and c1 to 'm' # This is the missing part! > --> change the choice to 'y' > --> do not change anything else > --> exit and save > > I spontaneously planned to answer with a modified config file with > default values 'm' specified for 'c0' and 'c1' (complete file below) but > I noticed that my latest patch does not help in that case. The first > patch that modifies sym_calc_value() would handle it nicely but the > latter one that modifies sym_calc_visibility() does not. The > combination also does not work, because sym_calc_visibility() influences > sym_calc_value(). [SNIP] Hi Yann, all, seems that I was a bit misleaded, here. While looking at how to possibly fix what I described, I realized that default values for choice values are not supported and therfore there is no issue: choices_kconfig:17:warning: defaults for choice values not supported choices_kconfig:22:warning: defaults for choice values not supported I noticed these warnings only accidently, when I was using an assert() that caused an abort and prevented the output to stderr being hidden by the ncurses output. Perhaps I should redirect stderr to a file and inspect it, in the future... So, my concerns with my own patch were unsubstantiated. Dirk > - Sample Kconfig ------------------------------------------------------- > > config modules > boolean modules > default y > option modules > > config dependency > tristate "Dependency" > default m > > choice > tristate "Tristate Choice" > default choice0 > > config choice0 > tristate "Choice 0" > default m > > config choice1 > tristate "Choice 1" > depends on dependency > default m > > endchoice > > ------------------------------------------------------------------------ -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
