Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1339507 > unrolled thread

Re: Re: [PATCH] PM / devfreq: tegra: Set freq in rate callback

Started byTomeu Vizoso <tomeu.vizoso@collabora.com>
First post2016-02-22 15:20 +0100
Last post2016-02-22 15:20 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Re: [PATCH] PM / devfreq: tegra: Set freq in rate callback Tomeu Vizoso <tomeu.vizoso@collabora.com> - 2016-02-22 15:20 +0100

#1339507 — Re: Re: [PATCH] PM / devfreq: tegra: Set freq in rate callback

FromTomeu Vizoso <tomeu.vizoso@collabora.com>
Date2016-02-22 15:20 +0100
SubjectRe: Re: [PATCH] PM / devfreq: tegra: Set freq in rate callback
Message-ID<r4Zvc-6YD-17@gated-at.bofh.it>
On 28 January 2016 at 05:14, MyungJoo Ham <myungjoo.ham@samsung.com> wrote:
>> Hi Thierry,
>>
>> On 21 January 2016 at 02:54, Thierry Reding <thierry.reding@gmail.com> wrote:
>> > On Thu, Jan 21, 2016 at 08:52:26AM +0100, Tomeu Vizoso wrote:
> []
>> >> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
>> >> Reported-by: Tyler Baker <tyler.baker@linaro.org>
> []
>> >>
>> >
>> > I had noticed it recently but hadn't got around to look into it, thanks
>> > for fixing it.
>> >
>> > Tested-by: Thierry Reding <treding@nvidia.com>
>> > Acked-by: Thierry Reding <treding@nvidia.com>
>>
>> I don't see this patch in -next yet, so I'm guess it hasn't been
>> applied. Any chance you could pick it up? This issue is now
>> manifesting in mainline, and causing ton of noise in the boot reports.
>>
>> Cheers,
>>
>> Tyler
>
>
> Hey, the patch appeared at the mailing list a week ago.
> Linux 4.5-rc1 appeared 3 days ago.
> The fastest possible for mainline inclusion is 4.5-rc2 or 3.
>
> You cannot simply expect the patch to be included in the maiinline that fast.

Hi MyungJoo Ham,

the problem is that linux-next has been showing that error in
multi_v7_defconfig builds since your changes got there. This is so
annoying that people have been putting their tegra124 boards offline
in their CI labs until this gets fixed in linux-next.

Regards,

Tomeu

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web