diff options
author | Scott Wood <swood@redhat.com> | 2017-07-16 19:16:23 -0500 |
---|---|---|
committer | Steven Rostedt (VMware) <rostedt@goodmis.org> | 2018-03-21 12:06:25 -0400 |
commit | edbd0ede0078bde5eb539e175cd7e0e89cd82df0 (patch) | |
tree | cd4965faa26c581e6dfd1073f29b7df9e2a38a0a /tools/testing/ktest | |
parent | 3e1d3678844b2b1f4c41818bc9a2885cbf5ccef6 (diff) |
ktest: Clarify config file usage
Simply telling a new user to edit "the config file" without giving any
hints on where that file should go, what it should be named, or where
a template can be found, is not particularly helpful.
Link: http://lkml.kernel.org/r/20170717001630.10518-1-swood@redhat.com
Signed-off-by: Scott Wood <swood@redhat.com>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'tools/testing/ktest')
-rwxr-xr-x | tools/testing/ktest/ktest.pl | 3 | ||||
-rw-r--r-- | tools/testing/ktest/sample.conf | 3 |
2 files changed, 5 insertions, 1 deletions
diff --git a/tools/testing/ktest/ktest.pl b/tools/testing/ktest/ktest.pl index a959b6f79ce5..c85a9f9342f4 100755 --- a/tools/testing/ktest/ktest.pl +++ b/tools/testing/ktest/ktest.pl @@ -1143,7 +1143,8 @@ sub __read_config { sub get_test_case { print "What test case would you like to run?\n"; print " (build, install or boot)\n"; - print " Other tests are available but require editing the config file\n"; + print " Other tests are available but require editing ktest.conf\n"; + print " (see tools/testing/ktest/sample.conf)\n"; my $ans = <STDIN>; chomp $ans; $default{"TEST_TYPE"} = $ans; diff --git a/tools/testing/ktest/sample.conf b/tools/testing/ktest/sample.conf index 8df62c837dd1..e628e7c8d875 100644 --- a/tools/testing/ktest/sample.conf +++ b/tools/testing/ktest/sample.conf @@ -1,6 +1,9 @@ # # Config file for ktest.pl # +# Place your customized version of this, named ktest.conf, in the +# working directory that ktest.pl is run from. +# # Note, all paths must be absolute # |