On Tue, Feb 5, 2013 at 1:59 AM, Zhang Rui wrote:
> On Mon, 2013-02-04 at 11:49 -0800, amit daniel kachhap wrote:
>> On Thu, Jan 31, 2013 at 11:59 PM, Zhang Rui wrote:
>> > On Thu, 2013-01-24 at 16:24 +0100, Gu1 wrote:
>> >> In different places in the Thermal code, the CPU frequency list is
>> >>
On Mon, 2013-02-04 at 11:49 -0800, amit daniel kachhap wrote:
> On Thu, Jan 31, 2013 at 11:59 PM, Zhang Rui wrote:
> > On Thu, 2013-01-24 at 16:24 +0100, Gu1 wrote:
> >> In different places in the Thermal code, the CPU frequency list is iterated
> >> in an incorrect way, leading to endless loops w
On Thu, Jan 24, 2013 at 7:24 AM, Gu1 wrote:
> In different places in the Thermal code, the CPU frequency list is iterated
> in an incorrect way, leading to endless loops when the frequency list contains
> a CPUFREQ_TABLE_INVALID entry, which is the case by default in the the Exynos
> 4x12 cpufreq
On Thu, Jan 31, 2013 at 11:59 PM, Zhang Rui wrote:
> On Thu, 2013-01-24 at 16:24 +0100, Gu1 wrote:
>> In different places in the Thermal code, the CPU frequency list is iterated
>> in an incorrect way, leading to endless loops when the frequency list
>> contains
>> a CPUFREQ_TABLE_INVALID entry,
On Thu, 2013-01-24 at 16:24 +0100, Gu1 wrote:
> In different places in the Thermal code, the CPU frequency list is iterated
> in an incorrect way, leading to endless loops when the frequency list contains
> a CPUFREQ_TABLE_INVALID entry, which is the case by default in the the Exynos
> 4x12 cpufreq
In different places in the Thermal code, the CPU frequency list is iterated
in an incorrect way, leading to endless loops when the frequency list contains
a CPUFREQ_TABLE_INVALID entry, which is the case by default in the the Exynos
4x12 cpufreq driver, for example.
The frequency list is iterated
6 matches
Mail list logo
