Steven Rostedt 0df213ca31 ktest: Require one TEST_START in config file ... There has been too many times that I put in one too many SKIP TEST_STARTs and start the test with the default randconfig by accident that I added this to have ktest ask the user for which test they want to run if no TEST_START is specified. Now if I accidently start the test with all TEST_STARTs skipped, ktest asks what test do I want to run, and I now have a chance to kill it before it does a make mrproper on my build directory. Signed-off-by: Steven Rostedt <rostedt@goodmis.org>		2011-06-14 20:51:37 -04:00
..
firewire	tools/firewire: nosy-dump: increment program version	2010-07-27 11:04:12 +02:00
perf	perf top: Don't stop if no kernel symtab is found	2011-05-27 16:02:29 -03:00
power/x86	Merge branch 'master' into for-next	2011-04-26 10:22:59 +02:00
slub	slub: move slabinfo.c to tools/slub/slabinfo.c	2010-11-06 09:04:32 +02:00
testing/ktest	ktest: Require one TEST_START in config file	2011-06-14 20:51:37 -04:00
usb	USB: ffs-test: fix header path	2011-02-28 19:27:12 -08:00
virtio	virtio_test: support event index	2011-05-30 11:14:15 +09:30