Re: [PATCH v2 0/8] Introduce new cpufreq helper macros

[Stratos Karafotis]

On 16/04/2014 07:01 ÏÎ, Viresh Kumar wrote:
> On 16 April 2014 03:55, Stratos Karafotis <stratosk@xxxxxxxxxxxx> wrote:
>> Hi all,
>>
>> This patch set introduces two freq_table helper macros which
>> can be used for iteration over cpufreq_frequency_table and
>> makes the necessary changes to cpufreq core and drivers that
>> use such an iteration procedure.
>>
>> The motivation was a usage of common procedure to iterate over
>> cpufreq_frequency_table across all drivers and cpufreq core.
>>
>> This was tested on a x86_64 platform.
>> Most files compiled successfully but unfortunately I was not
>> able to compile sh_sir.c pasemi_cpufreq.c and ppc_cbe_cpufreq.c
>> due to lack of cross compiler.
>>
>> Changes v1 -> v2
>>         - Rearrange patches
>>         - Remove redundant braces
>>         - Fix a newly introduced bug in exynos5440
>>         - Use cpufreq_for_each_valid_entry instead of
>> cpufreq_for_each_entry in cpufreq_frequency_table_get_index()
>>         - Drop redundant double ! operator in longhaul and change
> 
> You dropped this !! in thermal stuff and not longhaul :)
> 
>> the pos loop cursor variable to freq_pos.
>>         - Declare pos variable on a separate line
>>
>> Stratos Karafotis (8):
>>   cpufreq: Introduce macros for cpufreq_frequency_table iteration
>>   cpufreq: Use cpufreq_for_each_* macros for frequency table iteration
>>   davinci: da850: Use cpufreq_for_each_entry macro for iteration
>>   mips: lemote 2f: se cpufreq_for_each_entry macro for iteration
>>   mfd: db8500-prcmu: Use cpufreq_for_each_entry macro for iteration
>>   thermal: cpu_cooling: Use cpufreq_for_each_valid_entry macro for
>>     iteration
>>   irda: sh_sir: Use cpufreq_for_each_valid_entry macro for iteration
>>   sh: clk: Use cpufreq_for_each_valid_entry macro for iteration
> 
> Acked-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
> 

Thanks!

Stratos
--
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/