On Sat, Oct 9, 2010 at 1:49 AM, Bob Copeland <[email protected]> wrote: > On Fri, Oct 8, 2010 at 12:33 AM, Jonathan Guerin <[email protected]> > wrote: >>>> The ath5k STA/AP virtualization patch went in as well. Any chance you >>>> could bisect to see what patch causes the problem? >> >> I'm not familiar with doing it, but one of my colleagues is. I'll try >> to apply just that one patch to the 2.6.35 branch and see if it still >> occurs. > > One somewhat inefficient but easy way to bisect is to just try different > compat-wireless snapshots and find the earliest bad one. That should at > least narrow it down to the guilty patchset. > > Unfortunately, it may narrow it down to a few dozen unrelated patches > since they all tend to go in about the same time, but it may be a bit > less messy than git-based bisection. I usually do git bisect myself > but you need to be careful to properly handle build breakages and such.
Wow you weren't kidding about build breakages! Just to get this clear, after setting a build to 'bad', it will choose the next commit hash to use. Does it automatically then check that out, or do I need to: git checkout <hash> git reset --hard <hash> I may be getting this workflow a bit wrong... Thanks, Jonathan > > -- > Bob Copeland %% www.bobcopeland.com > _______________________________________________ ath5k-devel mailing list [email protected] https://lists.ath5k.org/mailman/listinfo/ath5k-devel
