On 22 August 2013 04:50, Rafael J. Wysocki wrote:
> OK, so the plan for merging this will be that we'll put 1 into linux-next
> and add 2 to it after a few days etc. to give people a chance to test one
> set of changes before going to the next one.
>
>> 1: cpufreq: Introduce
On Wednesday, August 21, 2013 08:12:19 PM Viresh Kumar wrote:
> Many CPUFreq drivers for SMP system (where all cores share same clock lines),
> do
> similar stuff in their ->init() part.
>
> This patch creates a generic routine in cpufreq core which can be used by
> these
> so that we can
Many CPUFreq drivers for SMP system (where all cores share same clock lines), do
similar stuff in their ->init() part.
This patch creates a generic routine in cpufreq core which can be used by these
so that we can remove some redundant code. And later part of patchset makes
other drivers use this
Many CPUFreq drivers for SMP system (where all cores share same clock lines), do
similar stuff in their -init() part.
This patch creates a generic routine in cpufreq core which can be used by these
so that we can remove some redundant code. And later part of patchset makes
other drivers use this
On Wednesday, August 21, 2013 08:12:19 PM Viresh Kumar wrote:
Many CPUFreq drivers for SMP system (where all cores share same clock lines),
do
similar stuff in their -init() part.
This patch creates a generic routine in cpufreq core which can be used by
these
so that we can remove some
On 22 August 2013 04:50, Rafael J. Wysocki r...@sisk.pl wrote:
OK, so the plan for merging this will be that we'll put 1 into linux-next
and add 2 to it after a few days etc. to give people a chance to test one
set of changes before going to the next one.
1: cpufreq: Introduce
6 matches
Mail list logo
