path: root/tools/testing/ktest/sample.conf
diff options
authorSteven Rostedt <srostedt@redhat.com>2012-05-21 23:35:12 -0400
committerSteven Rostedt <rostedt@goodmis.org>2012-05-22 00:07:34 -0400
commit43de3316e97c5a9ac4446aa33a893c15cea512b7 (patch)
treeac1b6df1655ab245cb013867becd682d6caa1eab /tools/testing/ktest/sample.conf
parentktest: Add MIN_CONFIG_TYPE to allow making a minum .config that has network (diff)
ktest: Add USE_OUTPUT_MIN_CONFIG to avoid prompt on make_min_config
If the file that OUTPUT_MIN_CONFIG exists then ktest.pl will prompt the user and ask them if the OUTPUT_MIN_CONFIG should be used as the starting point for make_min_config instead of MIN_CONFIG. This is usually the case, and to allow the user to do so, which is helpful if the user is creating different min configs based on tests, and they know one is a superset of another test, they can set USE_OUTPUT_MIN_CONFIG to one, which will prevent kest.pl from prompting to use the OUTPUT_MIN_CONFIG and it will just use it. If USE_OUTPUT_MIN_CONIFG is set to zero, then ktest.pl will continue to use MIN_CONFIG instead. The default is that USE_OUTPUT_MIN_CONFIG is undefined. Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to '')
1 files changed, 6 insertions, 0 deletions
diff --git a/tools/testing/ktest/sample.conf b/tools/testing/ktest/sample.conf
index 1c1b7dc13430..0e8191b6c5e3 100644
--- a/tools/testing/ktest/sample.conf
+++ b/tools/testing/ktest/sample.conf
@@ -1113,6 +1113,12 @@
# config that is generated allows network activity (ssh).
# (optional)
+# USE_OUTPUT_MIN_CONFIG set this to 1 if you do not want to be prompted
+# about using the OUTPUT_MIN_CONFIG as the MIN_CONFIG as the starting
+# point. Set it to 0 if you want to always just use the given MIN_CONFIG.
+# If it is not defined, it will prompt you to pick which config
+# to start with (MIN_CONFIG or OUTPUT_MIN_CONFIG).
# Example:
# TEST_TYPE = make_min_config