aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/kconfig/tests/new_choice_with_dep/expected_stdout
diff options
context:
space:
mode:
authorMasahiro Yamada <yamada.masahiro@socionext.com>2018-03-13 18:12:06 +0900
committerMasahiro Yamada <yamada.masahiro@socionext.com>2018-03-26 02:04:03 +0900
commitb76960c0f6b25d447a1493c4388defb9e8e76c63 (patch)
treed5f2fe0c6a19c2c609b93e119ea2badb6df02453 /scripts/kconfig/tests/new_choice_with_dep/expected_stdout
parentkconfig: tests: test automatic submenu creation (diff)
downloadlinux-dev-b76960c0f6b25d447a1493c4388defb9e8e76c63.tar.xz
linux-dev-b76960c0f6b25d447a1493c4388defb9e8e76c63.zip
kconfig: tests: test if new symbols in choice are asked
If new choice values are added with new dependency, and they become visible during user configuration, oldconfig should recognize them as (NEW), and ask the user for choice. This issue was fixed by commit 5d09598d488f ("kconfig: fix new choices being skipped upon config update"). This is a subtle corner case. Add a test case to avoid breakage. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Reviewed-by: Ulf Magnusson <ulfalizer@gmail.com>
Diffstat (limited to '')
-rw-r--r--scripts/kconfig/tests/new_choice_with_dep/expected_stdout10
1 files changed, 10 insertions, 0 deletions
diff --git a/scripts/kconfig/tests/new_choice_with_dep/expected_stdout b/scripts/kconfig/tests/new_choice_with_dep/expected_stdout
new file mode 100644
index 000000000000..74dc0bcb22bc
--- /dev/null
+++ b/scripts/kconfig/tests/new_choice_with_dep/expected_stdout
@@ -0,0 +1,10 @@
+A (A) [N/y/?] (NEW) y
+ Choice ?
+ > 1. Choice B (CHOICE_B)
+ 2. Choice C (CHOICE_C) (NEW)
+ choice[1-2?]:
+Choice2 ?
+ 1. Choice D (CHOICE_D)
+> 2. Choice E (CHOICE_E)
+ 3. Choice F (CHOICE_F) (NEW)
+choice[1-3?]: