On 06/30/2013 05:15 PM, Viresh Kumar wrote: > On 30 June 2013 19:52, Rafael J. Wysocki <rjw@xxxxxxx> wrote: >> Well, to be honest, I'm not really sure how the above commit can cause the >> problem you're seeing to happen ... >> >> Srivatsa, Viresh, any ideas? > > I don't. But its very simple to get this checked isn't it? > Just revert this patch on top of your kernel (leave bisect) and > see if gets fixed. > I do (mostly) check a bisect result before I post it to a mailing list to not blame the wrong commit to be guilty (b/c - erm - I did it in the past). Said that I finished bisect, checked out commit a66b2e5, tested it (has the issue), did "git show a66b2e5 | patch -p1 -R" and checked that result (no issue). -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3 -- 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
