https://bugzilla.kernel.org/show_bug.cgi?id=77201 --- Comment #36 from Viresh Kumar <viresh.kumar@xxxxxxxxxx> --- (In reply to Srivatsa S. Bhat from comment #35) > No, you misunderstood my intention. Of course your branch is a much > stricter one with all new cpufreq commits reverted. > > I was just trying to point out commits which came after 3.13.8, in case even > your branch (3.13.8 along with cpufreq reverts) ends up passing his tests. > In that case we'll have to narrow down *within* the commits between v3.13.8 > and v3.14.1, no? My list was to help with that. Ahh, sorry.. But in that case, wouldn't a git bisect between v3.13.8..my-branch would be easier? -- 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
