ktest.pl: Fix typo "accesing"There is a spelling mistake of 'accesing' in comments which shouldbe 'accessing'.Fixes: 6d76f469c8ac9 ("ktest: Add useful example configs")Link: https://lore.kernel
ktest.pl: Fix typo "accesing"There is a spelling mistake of 'accesing' in comments which shouldbe 'accessing'.Fixes: 6d76f469c8ac9 ("ktest: Add useful example configs")Link: https://lore.kernel.org/[email protected]Reviewed-by: SeongJae Park <[email protected]>Signed-off-by: WangYuli <[email protected]>Signed-off-by: Steven Rostedt <[email protected]>
show more ...
bootconfig/tracing/ktest: Add ktest examples of testing bootconfigbootconfig is a new feature that appends scripts onto the initrd, and thekernel executes the scripts as an extended kernel command
bootconfig/tracing/ktest: Add ktest examples of testing bootconfigbootconfig is a new feature that appends scripts onto the initrd, and thekernel executes the scripts as an extended kernel command line.Need to add tests to test that the happened. To test the bootconfigproperly, the initrd needs to be updated and the kernel rebooted. ktest isthe perfect solution to perform these tests.Add a example bootconfig.conf in the tools/testing/ktest/examples/includeand example bootconfig scripts in tools/testing/ktest/examples/bootconfigand also include verifier scripts that ktest will install on the targetand run to make sure that the bootconfig options in the scripts took placeafter the target rebooted with the new initrd update.Link: https://lkml.kernel.org/r/[email protected]Reviewed-by: Masami Hiramatsu <[email protected]>Signed-off-by: Steven Rostedt (VMware) <[email protected]>
ktest: Add make_warnings_file and process full warningsAlthough the patchcheck test checks for warnings in the files that werechanged, this check does not catch warnings that were caused by header
ktest: Add make_warnings_file and process full warningsAlthough the patchcheck test checks for warnings in the files that werechanged, this check does not catch warnings that were caused by headerfile changes and the warnings appear in C files not touched by thecommit.Add a new option called WARNINGS_FILE. If this option is set, then thefile it points to is read before bulid, and the file should contain alist of known warnings. If a warning appears in the build, this file ischecked, and if the warning does not exist in this file, then it failsthe build showing the new warning.If the WARNINGS_FILE points to a file that does not exist, this willcause any warning in the build to fail.A new test is also added called "make_warnings_file". This test willcreate do a build and record any warnings it finds into theWARNINGS_FILE. This test is something that can be run before other teststo build a warnings file of "known warnings", ie, warnings that werethere before your changes.Signed-off-by: Steven Rostedt <[email protected]>
tools/testing: fix comment / output typosCorrect spelling typo in tools/testingSigned-off-by: Masanari Iida <[email protected]>Signed-off-by: Jiri Kosina <[email protected]>
ktest: Add useful example configsI've been asked several times to provide more useful example configs forktest.pl, as the sample.conf is too complex (because it explains allconfigs). This adds co
ktest: Add useful example configsI've been asked several times to provide more useful example configs forktest.pl, as the sample.conf is too complex (because it explains allconfigs). This adds configs broken up by use case, and these configs arebased on actual configs that I use on a daily basis.Signed-off-by: Steven Rostedt <[email protected]>