hollalinux
/
linux-sg2042
mirror of https://github.com/sophgo/linux-riscv.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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>
This commit is contained in:
Scott Wood 2017-07-16 19:16:23 -05:00 committed by Steven Rostedt (VMware)
parent 3e1d367884
commit edbd0ede00
2 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
tools/testing/ktest/ktest.pl
View File

@ -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;

3
tools/testing/ktest/sample.conf
View File

@ -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
#