On Mon, Jun 16, 2014 at 4:01 PM, Erich Eickmeyer
<erich@xxxxxxxxxxxxxxxxxx> wrote:
>
> Here is the output from git-bisect:
>>
>> running 1860e379875dfe7271c649058aeddffe5afd9d0d is the first bad commit
Since that is just the commit that changes the version number, I'm
feeling pretty confident in saying that it looks like your bisection
must have failed.
If you end up marking something bad that wasn't (or vice versa), git
bisect will give bogus results. Sometimes it's just silly mistakes
(testing the wrong kernel versions, for example), sometimes it's
because the problem isn't 100% reproducible so that you mark a kernel
good even though it's bad (but only bad some of the time, depending on
timing or other randomness).
Linus
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html