https://bugzilla.kernel.org/show_bug.cgi?id=77201 --- Comment #39 from Srivatsa S. Bhat <srivatsa@xxxxxxx> --- (In reply to Viresh Kumar from comment #38) > (In reply to Srivatsa S. Bhat from comment #37) > > (In reply to Viresh Kumar from comment #36) > > > > But in that case, wouldn't a git bisect between v3.13.8..my-branch would be > > s/3.13.8/3.14 > > > > easier? > > > > Yes, a git bisect would have been ideal, but apparently it is failing due to > > build errors in intermediate commits (see his first report and bisect log) > > :-( > > So we might have to manually pick suspect commits to test... > > Does the above change make it any better ? > > We only have few revert patches (GOOD) on top of 3.14 (BAD) and can easily > make out which one is making 3.14 good :) I hope so :-) Regards, Srivatsa S. Bhat -- You are receiving this mail because: You are the assignee for the bug. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
