On 2 June 2016 at 20:38, Rafael J. Wysocki <[email protected]> wrote: > On Thu, Jun 2, 2016 at 4:19 PM, Viresh Kumar <[email protected]> wrote: >> Hi Rafael, >> >> This series fixes all cpufreq drivers that provide a 'target_index' >> callback or in other words, which provide a freq-table to cpufreq core, >> to make sure they *only* use the 'index' argument to ->target_index() >> with the policy->freq_table. >> >> This change allows us to remove the (duplicate) sorted-freq-table, which >> was added by following series: >> >> [PATCH V2 0/2] cpufreq: Use sorted frequency tables > > Which I'm not going to apply. > > If this series depended on that one, please rework it.
Hi Rafael, The first 9 patches can be applied without any dependency on the earlier series, but not the last two. The target of this series is to make freq-table lookup faster and so most of its patches would make sense only if we are trying to solve that problem. Otherwise they may not be required at all. I hope that you will be replying to the earlier series [1] as well, to convey the concerns you have with it. Thanks -- viresh [1] [PATCH V2 0/2] cpufreq: Use sorted frequency tables
