Steven Rostedt (Red Hat) c4d1d11f3b ktest: Put back in the CONFIG_BISECT_CHECK ... The new rewrite left out the CONFIG_BISECT_CHECK, which allows the user to test that their "bad" config still is bad and their "good" config still is good. This is especially important as the configs are passed through a "make oldconfig" to update them with the lastest kernel. Things could change that causes a bad config to work, or a good config to break. The check is done after the configs have run through the oldconfig processing. Signed-off-by: Steven Rostedt <rostedt@goodmis.org>		2014-04-23 23:18:20 -04:00
..
examples	ktest: Set CLOSE_CONSOLE_SIGNAL in the kvm.conf	2014-02-26 15:26:24 -05:00
compare-ktest-sample.pl	ktest: Fix compare script to test if options are not documented	2011-12-22 22:06:59 -05:00
ktest.pl	ktest: Put back in the CONFIG_BISECT_CHECK	2014-04-23 23:18:20 -04:00
sample.conf	ktest: Add BISECT_TRIES to bisect test	2014-01-18 19:52:13 -05:00