diff options
author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2018-03-13 18:12:10 +0900 |
---|---|---|
committer | Masahiro Yamada <yamada.masahiro@socionext.com> | 2018-03-26 02:04:04 +0900 |
commit | 3e4888c2e3d77d70edb905364cd70059a52a1343 (patch) | |
tree | 2ae6e086d4442cc153be0e4d73c787fd3c98c45c /drivers/power | |
parent | beaaddb625400e4a561d2d8443f9df2aa3f9a899 (diff) | |
download | op-kernel-dev-3e4888c2e3d77d70edb905364cd70059a52a1343.zip op-kernel-dev-3e4888c2e3d77d70edb905364cd70059a52a1343.tar.gz |
kconfig: tests: test randconfig for choice in choice
Commit 3b9a19e08960 ("kconfig: loop as long as we changed some symbols
in randconfig") fixed randconfig where a choice contains a sub-choice.
Prior to that commit, the sub-choice values were not set.
I am not sure whether this is an intended feature or just something
people discovered works, but it is used in the real world;
drivers/usb/gadget/legacy/Kconfig is source'd in a choice context,
then creates a sub-choice in it.
For the test case in this commit, there are 3 possible results.
Case 1:
CONFIG_A=y
# CONFIG_B is not set
Case 2:
# CONFIG_A is not set
CONFIG_B=y
CONFIG_C=y
# CONFIG_D is not set
Case 3:
# CONFIG_A is not set
CONFIG_B=y
# CONFIG_C is not set
CONFIG_D=y
CONFIG_E=y
So, this test iterates several times, and checks if the result is
either of the three.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: Ulf Magnusson <ulfalizer@gmail.com>
Diffstat (limited to 'drivers/power')
0 files changed, 0 insertions, 0 deletions