On 28 January 2016 at 05:14, MyungJoo Ham wrote:
>> Hi Thierry,
>>
>> On 21 January 2016 at 02:54, Thierry Reding wrote:
>> > On Thu, Jan 21, 2016 at 08:52:26AM +0100, Tomeu Vizoso wrote:
> []
>> >> Signed-off-by: Tomeu Vizoso
On 28 January 2016 at 05:14, MyungJoo Ham wrote:
>> Hi Thierry,
>>
>> On 21 January 2016 at 02:54, Thierry Reding wrote:
>> > On Thu, Jan 21, 2016 at 08:52:26AM +0100, Tomeu Vizoso wrote:
> []
>> >> Signed-off-by: Tomeu Vizoso
>> >> Reported-by: Tyler Baker
> []
>> >>
>> >
>> > I had noticed
On 27 January 2016 at 20:14, MyungJoo Ham wrote:
>> Hi Thierry,
>>
>> On 21 January 2016 at 02:54, Thierry Reding wrote:
>> > On Thu, Jan 21, 2016 at 08:52:26AM +0100, Tomeu Vizoso wrote:
> []
>> >> Signed-off-by: Tomeu Vizoso
>> >> Reported-by: Tyler Baker
> []
>> >>
>> >
>> > I had noticed
On 27 January 2016 at 20:14, MyungJoo Ham wrote:
>> Hi Thierry,
>>
>> On 21 January 2016 at 02:54, Thierry Reding wrote:
>> > On Thu, Jan 21, 2016 at 08:52:26AM +0100, Tomeu Vizoso wrote:
> []
>> >> Signed-off-by: Tomeu Vizoso
> Hi Thierry,
>
> On 21 January 2016 at 02:54, Thierry Reding wrote:
> > On Thu, Jan 21, 2016 at 08:52:26AM +0100, Tomeu Vizoso wrote:
[]
> >> Signed-off-by: Tomeu Vizoso
> >> Reported-by: Tyler Baker
[]
> >>
> >
> > I had noticed it recently but hadn't got around to look into it, thanks
> >
Hi Thierry,
On 21 January 2016 at 02:54, Thierry Reding wrote:
> On Thu, Jan 21, 2016 at 08:52:26AM +0100, Tomeu Vizoso wrote:
>> As per the documentation of the devfreq_dev_profile.target callback, set
>> the freq argument to the new frequency before returning.
>>
>> This caused endless
> Hi Thierry,
>
> On 21 January 2016 at 02:54, Thierry Reding wrote:
> > On Thu, Jan 21, 2016 at 08:52:26AM +0100, Tomeu Vizoso wrote:
[]
> >> Signed-off-by: Tomeu Vizoso
> >> Reported-by: Tyler Baker
[]
> >>
> >
> >
Hi Thierry,
On 21 January 2016 at 02:54, Thierry Reding wrote:
> On Thu, Jan 21, 2016 at 08:52:26AM +0100, Tomeu Vizoso wrote:
>> As per the documentation of the devfreq_dev_profile.target callback, set
>> the freq argument to the new frequency before returning.
>>
>>
On Thu, Jan 21, 2016 at 08:52:26AM +0100, Tomeu Vizoso wrote:
> As per the documentation of the devfreq_dev_profile.target callback, set
> the freq argument to the new frequency before returning.
>
> This caused endless messages like this after recent changes in the core:
>
> devfreq
>As per the documentation of the devfreq_dev_profile.target callback, set
>the freq argument to the new frequency before returning.
>
>This caused endless messages like this after recent changes in the core:
>
>devfreq 6000c800.actmon: Couldn't update frequency transition information.
>
On Thu, Jan 21, 2016 at 08:52:26AM +0100, Tomeu Vizoso wrote:
> As per the documentation of the devfreq_dev_profile.target callback, set
> the freq argument to the new frequency before returning.
>
> This caused endless messages like this after recent changes in the core:
>
> devfreq
>As per the documentation of the devfreq_dev_profile.target callback, set
>the freq argument to the new frequency before returning.
>
>This caused endless messages like this after recent changes in the core:
>
>devfreq 6000c800.actmon: Couldn't update frequency transition information.
>
12 matches
Mail list logo