Messages in this thread | | | Subject | Re: Resend: [PATCH] ktest: Fix typos in sample.conf | From | Randy Dunlap <> | Date | Mon, 22 Jul 2019 15:20:35 -0700 |
| |
On 7/22/19 3:17 PM, Masanari Iida wrote: > This patch fixes some spelling typos in sample.conf. > > Signed-off-by: Masanari Iida <standby24x7@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> --- > tools/testing/ktest/sample.conf | 20 ++++++++++---------- > 1 file changed, 10 insertions(+), 10 deletions(-) > > diff --git a/tools/testing/ktest/sample.conf b/tools/testing/ktest/sample.conf > index c3bc933d437b..f31d6dcf2f99 100644 > --- a/tools/testing/ktest/sample.conf > +++ b/tools/testing/ktest/sample.conf > @@ -10,7 +10,7 @@ > # > > # 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: > # > # LOG_FILE > @@ -204,7 +204,7 @@ > # > # This config file can also contain "config variables". > # These are assigned with ":=" instead of the ktest option > -# assigment "=". > +# assignment "=". > # > # The difference between ktest options and config variables > # is that config variables can be used multiple times, > @@ -263,7 +263,7 @@ > #### Using options in other options #### > # > # 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 > # processing time). > # > @@ -707,7 +707,7 @@ > > # Line to define a successful boot up in console output. > # 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) > # > # SUCCESS_LINE = ^MyBox Login:$ > @@ -839,7 +839,7 @@ > # (ignored if POWEROFF_ON_SUCCESS is set) > #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 > # reboot. > # Note, POWERCYCLE_AFTER_REBOOT = 0 does NOT disable it. It just > @@ -848,7 +848,7 @@ > # (default undefined) > #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 > # halt. > # Note, POWEROFF_AFTER_HALT = 0 does NOT disable it. It just > @@ -1093,7 +1093,7 @@ > # whatever reason. (Can't reboot, want to inspect each iteration) > # Doing a BISECT_MANUAL will have the test wait for you to > # 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. > # > # BISECT_CHECK = 1 (optional, default 0) > @@ -1124,13 +1124,13 @@ > # > # BISECT_RET_GOOD = 0 (optional, default undefined) > # > -# In case the specificed test returns something other than just > +# In case the specified test returns something other than just > # 0 for good, and non-zero for bad, you can override 0 being > # good by defining BISECT_RET_GOOD. > # > # BISECT_RET_BAD = 1 (optional, default undefined) > # > -# In case the specificed test returns something other than just > +# In case the specified test returns something other than just > # 0 for good, and non-zero for bad, you can override non-zero being > # bad by defining BISECT_RET_BAD. > # > @@ -1239,7 +1239,7 @@ > # > # CONFIG_BISECT_EXEC (optional) > # 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. > # If it does not find it there, it will look for: > # `dirname <ktest.pl>`/config-bisect.pl # The directory that holds ktest.pl >
-- ~Randy
| |