On 03-06-16, 03:43, Rafael J. Wysocki wrote:
> On Friday, June 03, 2016 05:31:34 AM Viresh Kumar wrote:
> > So, yeah, I get your overall concern. What about this:
> > - A single patchset to make sure the current policy->freq_table is
> > always sorted in Ascending order of frequencies.
>
> Be
On 03-06-16, 03:43, Rafael J. Wysocki wrote:
> On Friday, June 03, 2016 05:31:34 AM Viresh Kumar wrote:
> > So, yeah, I get your overall concern. What about this:
> > - A single patchset to make sure the current policy->freq_table is
> > always sorted in Ascending order of frequencies.
>
> Be
On Friday, June 03, 2016 05:31:34 AM Viresh Kumar wrote:
> On 02-06-16, 22:35, Rafael J. Wysocki wrote:
> > Quoting from this very cover letter "This change allows us to remove
> > the (duplicate) sorted-freq-table, which
> > was added by following series:", so why to add it in the first place?
>
On Friday, June 03, 2016 05:31:34 AM Viresh Kumar wrote:
> On 02-06-16, 22:35, Rafael J. Wysocki wrote:
> > Quoting from this very cover letter "This change allows us to remove
> > the (duplicate) sorted-freq-table, which
> > was added by following series:", so why to add it in the first place?
>
On 02-06-16, 22:35, Rafael J. Wysocki wrote:
> Quoting from this very cover letter "This change allows us to remove
> the (duplicate) sorted-freq-table, which
> was added by following series:", so why to add it in the first place?
Okay, that's fine.
> Besides, there already is a number of tables
On 02-06-16, 22:35, Rafael J. Wysocki wrote:
> Quoting from this very cover letter "This change allows us to remove
> the (duplicate) sorted-freq-table, which
> was added by following series:", so why to add it in the first place?
Okay, that's fine.
> Besides, there already is a number of tables
On Thu, Jun 2, 2016 at 5:42 PM, Viresh Kumar wrote:
> On 2 June 2016 at 20:38, Rafael J. Wysocki wrote:
>> On Thu, Jun 2, 2016 at 4:19 PM, Viresh Kumar wrote:
>>> Hi Rafael,
>>>
>>> This series fixes all cpufreq drivers that
On Thu, Jun 2, 2016 at 5:42 PM, Viresh Kumar wrote:
> On 2 June 2016 at 20:38, Rafael J. Wysocki wrote:
>> On Thu, Jun 2, 2016 at 4:19 PM, Viresh Kumar wrote:
>>> Hi Rafael,
>>>
>>> This series fixes all cpufreq drivers that provide a 'target_index'
>>> callback or in other words, which provide
On 2 June 2016 at 20:38, Rafael J. Wysocki wrote:
> On Thu, Jun 2, 2016 at 4:19 PM, Viresh Kumar 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
On 2 June 2016 at 20:38, Rafael J. Wysocki wrote:
> On Thu, Jun 2, 2016 at 4:19 PM, Viresh Kumar 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*
On Thu, Jun 2, 2016 at 4:19 PM, Viresh Kumar 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
On Thu, Jun 2, 2016 at 4:19 PM, Viresh Kumar 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
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
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
14 matches
Mail list logo