Enrico Tagliavini <enrico.tagliavini@xxxxxxxxx> writes: > Yeah that's what I meant. My idea was to first bisect only the ath10k > directory, so restricting the bisect on the commits touching stuff > there. I guess if the issue is more broad it will come up somewhere > else as well, so this is a good starting point, I hope. Thank you for > pointing it out though, this will actually be the first time I do a > proper bisect. And remember to always to mention if you have restricted the bisect somehow, that's important information. And better if you provide 'git bisect log' output as well. > Also do you want me to bisect Kalle's sources or Linus' master? By > what Michał said I guess Kalle's but I ask to be sure. > > Also to be clear: I'm using Linus' sources at the moment, as provided > by Fedora rawhide. > > For me it's the same, so let me know what you prefer and is more > useful to solve this issue. Good that you brought this up. As ath.git master branch gets rebased every rc1 release you really cannot use that for bisect. Either you should use ath.git ath-next branch or Linus' tree. To be on the safe side I always recommend to use Linus' tree if at all possible. -- Kalle Valo -- 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
