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

Kalle Valo kvalo at qca.qualcomm.com
Tue Jul 28 23:54:06 PDT 2015

Michal Kazior <michal.kazior at tieto.com> writes:

>> This wont work for bisecting. I have to setup something else. Is
>> it ok if I restrict the bisect on the ath10k tree? That has enough
>> commit already to begin with, plus I'm going to be on the road in less
>> than two weeks.
> As long as you establish a working and a non-working commit id on
> kvalo tree it should be fine I guess.

And you can always limit the bisect to a certain directory, but the risk
here is that if the regression is outside ath10k bisect won't find it.
So you need to carefully consider is it safe to do or not. From the man

"Cutting down bisection by giving more parameters to bisect start

       You can further cut down the number of trials, if you know what
       part of the tree is involved in the problem you are tracking
       down, by specifying path parameters when issuing the bisect start

           $ git bisect start -- arch/i386 include/asm-i386"

Also if you can even just narrow down the regression to a smaller set of
patches, let's say few hundred, might make it easier to find the

Kalle Valo

More information about the ath10k mailing list