Christian Couder wrote:
You use "git bisect good v2.6.22", but this is not true because the
tag "v2.6.22" is on the mainstream kernel branch and the driver is not
there.
If the v2.6.22 kernel that used to work came directly from John Linville's
wireless-dev git tree, not from a patch, then you should find the exact
commit in John Linville's tree that worked and say "git bisect good <this
commit>".
But if the driver that worked with a mainstream v2.6.22 kernel had been
patched, and now doesn't work when the same patch is applied to mainstream
v2.6.23-rc1 kernel, then you can perhaps use:
git bisect start
git bisect bad v2.6.23-rc1
git bisect good v2.6.22
and then:
1) patch the kernel with the driver patch,
2) test the patched kernel,
3) remove the patch,
4) say "git bisect good" or "git bisect bad"
5) go to step 1) until the commit that broke the driver is found
Has the ability to use a commit hash to indicate a start point been in git for a long time? I think
I remember trying it before when a version tag had not been downloaded and having a failure.
Larry
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
