On 06/29/2014 04:32 AM, lolilolicon wrote:
On Sun, Jun 29, 2014 at 8:37 AM, Larry Finger <Larry.Finger@xxxxxxxxxxxx> wrote:
Something went wrong in your bisection. Commit 88daf80 is a merge commit and
is unlikely to be the bad one. You might try a checkout of b080e04 and try
it to see if it is bad or good. That is the first non-merge commit before
88daf80.
Larry
I have no clue how you identified b080e04, but I tested it and it is good.
I'm not good at git so please bear with me. What I know is 88daf80 is
bad, and both its two parents 010d3c3 and 35582ad are good: does that
not mean 88daf80 is the first bad commit?
% git bisect start 88daf80 010d3c3 35582ad
88daf80dcca19ff995cc263592426f734a9702f3 is the first bad commit
What am I getting wrong?
I am not an expert in git, but I think you are being too restrictive with that
command. If you do "git bisect start 88daf80 010d3c3", there are ath9k patches
in the code left to test. With the other option "git bisect start 88daf80
35582ad", git visualize does not show any ath9k changes.
Larry
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
