Commit afbac6c5 authored by Masanari Iida's avatar Masanari Iida Committed by Steven Rostedt (VMware)

ktest: Fix some typos in sample.conf

This patch fixes some spelling typo in sample.conf

Link: http://lkml.kernel.org/r/20190930124925.20250-1-standby24x7@gmail.comAcked-by: default avatarRandy Dunlap <rdunlap@infradead.org>
Signed-off-by: default avatarMasanari Iida <standby24x7@gmail.com>
Signed-off-by: default avatarSteven Rostedt (VMware) <rostedt@goodmis.org>
parent 98d54f81
...@@ -10,7 +10,7 @@ ...@@ -10,7 +10,7 @@
# #
# Options set in the beginning of the file are considered to be # Options set in the beginning of the file are considered to be
# default options. These options can be overriden by test specific # default options. These options can be overridden by test specific
# options, with the following exceptions: # options, with the following exceptions:
# #
# LOG_FILE # LOG_FILE
...@@ -204,7 +204,7 @@ ...@@ -204,7 +204,7 @@
# #
# This config file can also contain "config variables". # This config file can also contain "config variables".
# These are assigned with ":=" instead of the ktest option # These are assigned with ":=" instead of the ktest option
# assigment "=". # assignment "=".
# #
# The difference between ktest options and config variables # The difference between ktest options and config variables
# is that config variables can be used multiple times, # is that config variables can be used multiple times,
...@@ -263,7 +263,7 @@ ...@@ -263,7 +263,7 @@
#### Using options in other options #### #### Using options in other options ####
# #
# Options that are defined in the config file may also be used # Options that are defined in the config file may also be used
# by other options. All options are evaulated at time of # by other options. All options are evaluated at time of
# use (except that config variables are evaluated at config # use (except that config variables are evaluated at config
# processing time). # processing time).
# #
...@@ -707,7 +707,7 @@ ...@@ -707,7 +707,7 @@
# Line to define a successful boot up in console output. # Line to define a successful boot up in console output.
# This is what the line contains, not the entire line. If you need # This is what the line contains, not the entire line. If you need
# the entire line to match, then use regural expression syntax like: # the entire line to match, then use regular expression syntax like:
# (do not add any quotes around it) # (do not add any quotes around it)
# #
# SUCCESS_LINE = ^MyBox Login:$ # SUCCESS_LINE = ^MyBox Login:$
...@@ -839,7 +839,7 @@ ...@@ -839,7 +839,7 @@
# (ignored if POWEROFF_ON_SUCCESS is set) # (ignored if POWEROFF_ON_SUCCESS is set)
#REBOOT_ON_SUCCESS = 1 #REBOOT_ON_SUCCESS = 1
# In case there are isses with rebooting, you can specify this # In case there are issues with rebooting, you can specify this
# to always powercycle after this amount of time after calling # to always powercycle after this amount of time after calling
# reboot. # reboot.
# Note, POWERCYCLE_AFTER_REBOOT = 0 does NOT disable it. It just # Note, POWERCYCLE_AFTER_REBOOT = 0 does NOT disable it. It just
...@@ -848,7 +848,7 @@ ...@@ -848,7 +848,7 @@
# (default undefined) # (default undefined)
#POWERCYCLE_AFTER_REBOOT = 5 #POWERCYCLE_AFTER_REBOOT = 5
# In case there's isses with halting, you can specify this # In case there's issues with halting, you can specify this
# to always poweroff after this amount of time after calling # to always poweroff after this amount of time after calling
# halt. # halt.
# Note, POWEROFF_AFTER_HALT = 0 does NOT disable it. It just # Note, POWEROFF_AFTER_HALT = 0 does NOT disable it. It just
...@@ -972,7 +972,7 @@ ...@@ -972,7 +972,7 @@
# #
# PATCHCHECK_START is required and is the first patch to # PATCHCHECK_START is required and is the first patch to
# test (the SHA1 of the commit). You may also specify anything # test (the SHA1 of the commit). You may also specify anything
# that git checkout allows (branch name, tage, HEAD~3). # that git checkout allows (branch name, tag, HEAD~3).
# #
# PATCHCHECK_END is the last patch to check (default HEAD) # PATCHCHECK_END is the last patch to check (default HEAD)
# #
...@@ -994,7 +994,7 @@ ...@@ -994,7 +994,7 @@
# IGNORE_WARNINGS is set for the given commit's sha1 # IGNORE_WARNINGS is set for the given commit's sha1
# #
# IGNORE_WARNINGS can be used to disable the failure of patchcheck # IGNORE_WARNINGS can be used to disable the failure of patchcheck
# on a particuler commit (SHA1). You can add more than one commit # on a particular commit (SHA1). You can add more than one commit
# by adding a list of SHA1s that are space delimited. # by adding a list of SHA1s that are space delimited.
# #
# If BUILD_NOCLEAN is set, then make mrproper will not be run on # If BUILD_NOCLEAN is set, then make mrproper will not be run on
...@@ -1093,7 +1093,7 @@ ...@@ -1093,7 +1093,7 @@
# whatever reason. (Can't reboot, want to inspect each iteration) # whatever reason. (Can't reboot, want to inspect each iteration)
# Doing a BISECT_MANUAL will have the test wait for you to # Doing a BISECT_MANUAL will have the test wait for you to
# tell it if the test passed or failed after each iteration. # tell it if the test passed or failed after each iteration.
# This is basicall the same as running git bisect yourself # This is basically the same as running git bisect yourself
# but ktest will rebuild and install the kernel for you. # but ktest will rebuild and install the kernel for you.
# #
# BISECT_CHECK = 1 (optional, default 0) # BISECT_CHECK = 1 (optional, default 0)
...@@ -1239,7 +1239,7 @@ ...@@ -1239,7 +1239,7 @@
# #
# CONFIG_BISECT_EXEC (optional) # CONFIG_BISECT_EXEC (optional)
# The config bisect is a separate program that comes with ktest.pl. # The config bisect is a separate program that comes with ktest.pl.
# By befault, it will look for: # By default, it will look for:
# `pwd`/config-bisect.pl # the location ktest.pl was executed from. # `pwd`/config-bisect.pl # the location ktest.pl was executed from.
# If it does not find it there, it will look for: # If it does not find it there, it will look for:
# `dirname <ktest.pl>`/config-bisect.pl # The directory that holds ktest.pl # `dirname <ktest.pl>`/config-bisect.pl # The directory that holds ktest.pl
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment