QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

Enrico Tagliavini enrico.tagliavini at gmail.com
Wed Jul 29 07:22:24 PDT 2015

Sound! I'll keep a copy of the log then. If the bisect on ath10k
folder will lead nowhere I'll see if I can make it over the whole
tree. At least by doing it on the ath10k tree I hope to narrow down
the number of commit.

Ok then I'll use Linus' master, no problem with this.

I hope to at least get started this weekend.

On 29 July 2015 at 11:30, Kalle Valo <kvalo at qca.qualcomm.com> wrote:
> Enrico Tagliavini <enrico.tagliavini at gmail.com> 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

More information about the ath10k mailing list