Re: [PATCH 0/9] CPUFreq Updates & Fixes for 3.10

[Rafael J. Wysocki]

On Monday, April 01, 2013 06:27:40 PM Viresh Kumar wrote:
> Hi Rafael,
> 
> These are fixes and updates that are sent and reviewed as separate patchsets
> earlier. They are all now combined as part of a single patchset for you to apply
> in your linux-next branch.
> 
> All have got reviews earlier and got fixups mailed and applied.
> 
> The remaining patches: "Move Cpufreq drivers to drivers/cpufreq" are awaiting
> few more Acks before I send them to you.
> 
> I wanted to have another patch as part of this patchset, but I am awaiting Ack
> for it:
> tools: cpufreq: Fix cpufreq-info print messages for affected[related]_cpus
> 
> That can be applied separately once it receives an Ack.
> 
> Thanks
> Viresh
> 
> Viresh Kumar (9):
>   cpufreq: cpu0: Fix mistake in Documentation example
>   cpufreq: Documentation: Fix cpufreq_frequency_table name
>   cpufreq: cpufreq-cpu0: No need to check cpu number in init()
>   cpufreq: cpufreq-cpu0: Call CPUFREQ_POSTCHANGE notifier for failure
>     cases too
>   cpufreq: Notify all policy->cpus in cpufreq_notify_transition()
>   cpufreq: Don't check if cpu is online/offline for cpufreq callbacks
>   cpufreq: drivers: don't check range of target freq in .target()
>   cpufreq: drivers: Remove unnecessary assignments of policy-> members
>   cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue

Thanks!

The [5/9] seems to be missing.  Care to send?

Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/