ktest: Add BISECT_FILES to run git bisect on paths

Add the config option BISECT_FILES that allows the user to
specify what path in the kernel to run the git bisect on.

Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
This commit is contained in:
Steven Rostedt 2011-03-08 09:38:12 -05:00 committed by Steven Rostedt
parent c23dca7cd2
commit 3410f6fd5e
2 changed files with 17 additions and 1 deletions

View file

@ -1280,6 +1280,13 @@ sub bisect {
my $type = $opt{"BISECT_TYPE[$i]"};
my $start = $opt{"BISECT_START[$i]"};
my $replay = $opt{"BISECT_REPLAY[$i]"};
my $start_files = $opt{"BISECT_FILES[$i]"};
if (defined($start_files)) {
$start_files = " -- " . $start_files;
} else {
$start_files = "";
}
# convert to true sha1's
$good = get_sha1($good);
@ -1333,7 +1340,7 @@ sub bisect {
die "Failed to checkout $head";
}
run_command "git bisect start" or
run_command "git bisect start$start_files" or
dodie "could not start bisect";
run_command "git bisect good $good" or

View file

@ -528,6 +528,15 @@
# when something other than the BISECT_TYPE fails, ktest.pl will
# run "git bisect skip" and try again.
#
# BISECT_FILES = <path> (optional, default undefined)
#
# To just run the git bisect on a specific path, set BISECT_FILES.
# For example:
#
# BISECT_FILES = arch/x86 kernel/time
#
# Will run the bisect with "git bisect start -- arch/x86 kernel/time"
#
# BISECT_REVERSE = 1 (optional, default 0)
#
# In those strange instances where it was broken forever