W dniu 7 maja 2011 02:34 uÅytkownik Ben Greear <greearb@xxxxxxxxxxxxxxx> napisaÅ: > On 05/06/2011 04:51 PM, RafaÅ MiÅecki wrote: >> >> I suspect we have some ugly (hard trackable) regression between >> mainline and wireless-testing. It sounds impossible, but this seems to >> affect Broadcom cards and looks like not related to ssb or b43. >> >> Today I've compiled 2.6.38 and 2.6.39-rc6, both work GOOD. >> I've compiled wireless-testing and it failed, BAD. >> I've reverted all recent ssb patches from top and it still fails BAD. >> >> What would be the easiest way to try bisecting? I can see >> wireless-testing merges mainline quite often. Can I use some trick on >> checkouted wireless-testing? Do I have to checkout mainline and merge >> wireless-testing into it? Something even different? >> > > git bisect can handle it...I've spent some quality time finding > bugs in ath9k with that lately... Sure it can ;) But what should I match as GOOD for first bisect? wireless-testing merges mainline all the time. So there are wireless-testing specific commits between John's merge of 2.6.39-rc5 and 2.6.39-rc6. I can not match Linus's 2.6.39-rc6 as GOOD, because I won't test wireless-testing specific changes done earlier (these that didn't go info mainline). Maybe I should call GOOD a commit that wireless-testing is based on? Which one would it be? Or maybe I could rebase wireless-testing on mainline and then I could use 2.6.39-rc6 as GOOD? -- RafaÅ -- 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
