On Saturday, March 30, 2013 09:06:37 AM Viresh Kumar wrote: > On 30 March 2013 07:47, Rafael J. Wysocki <rjw@xxxxxxx> wrote: > > On Wednesday, March 27, 2013 09:28:56 PM Viresh Kumar wrote: > > >> To test these over linux-next you need to revert following first: > >> db9baec cpufreq: Get rid of "struct global_attr" > >> 86bd6f0 cpufreq: governor: Implement per policy instances of governors > >> 8ae67b1 cpufreq: Add per policy governor-init/exit infrastructure > > > I've applied these two patches and re-applied the queue on top of them. > > > > All is in my linux-next branch now. > > You were supposed to remove below patch too, which you missed :) > > c7baa5e cpufreq: Get rid of "struct global_attr" OK, I'll remove it. And by the way, I'm no longer amused with the mess going on in the cpufreq land. Please send me *patches*. I'm not interested in git pointers. Moreover, please send those patches in a way allowing me to figure out the ordering without looking into your git tree. If you have a number of outstanding cpufreq patches for me to apply, please create a patch series out of them and send it. Thanks, Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- 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
