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


Groups > linux.kernel > #1320277 > unrolled thread

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

Started byMyungJoo Ham <myungjoo.ham@samsung.com>
First post2016-01-28 05:20 +0100
Last post2016-01-29 00:10 +0100
Articles 2 — 2 participants

Back to article view | Back to linux.kernel


Contents

  Re: Re: [PATCH] PM / devfreq: tegra: Set freq in rate callback MyungJoo Ham <myungjoo.ham@samsung.com> - 2016-01-28 05:20 +0100
    Re: Re: [PATCH] PM / devfreq: tegra: Set freq in rate callback Tyler Baker <tyler.baker@linaro.org> - 2016-01-29 00:10 +0100

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

FromMyungJoo Ham <myungjoo.ham@samsung.com>
Date2016-01-28 05:20 +0100
SubjectRe: Re: [PATCH] PM / devfreq: tegra: Set freq in rate callback
Message-ID<qVMdQ-695-3@gated-at.bofh.it>
> 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.

[toc] | [next] | [standalone]


#1321125

FromTyler Baker <tyler.baker@linaro.org>
Date2016-01-29 00:10 +0100
Message-ID<qW3Rn-28Y-7@gated-at.bofh.it>
In reply to#1320277
On 27 January 2016 at 20: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.

I agree, and I was not asking for this patch to be included into
mainline yet, just that it would be applied to maintainers tree so it
could be included in linux-next. I want to ensure this issue is not
masking other issues in linux-next.

Cheers,

Tyler

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web