On 28 January 2016 at 05:14, MyungJoo Ham <myungjoo.ham@xxxxxxxxxxx> wrote: >> Hi Thierry, >> >> On 21 January 2016 at 02:54, Thierry Reding <thierry.reding@xxxxxxxxx> wrote: >> > On Thu, Jan 21, 2016 at 08:52:26AM +0100, Tomeu Vizoso wrote: > [] >> >> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@xxxxxxxxxxxxx> >> >> Reported-by: Tyler Baker <tyler.baker@xxxxxxxxxx> > [] >> >> >> > >> > I had noticed it recently but hadn't got around to look into it, thanks >> > for fixing it. >> > >> > Tested-by: Thierry Reding <treding@xxxxxxxxxx> >> > Acked-by: Thierry Reding <treding@xxxxxxxxxx> >> >> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
