Re: clk/clk-next bisection: boot on tegra124-nyan-big

From: Stephen Boyd
Date: Fri Nov 22 2019 - 12:01:44 EST


Quoting Guillaume Tucker (2019-11-20 00:17:28)
> On 20/11/2019 05:25, kernelci.org bot wrote:
> > Author: Thierry Reding <treding@xxxxxxxxxx>
> > Date: Thu Jul 25 18:19:00 2019 +0200
> >
> > clk: tegra: Reimplement SOR clock on Tegra124
> >
> > In order to allow the display driver to deal uniformly with all SOR
> > generations, implement the SOR clocks in a way that is compatible with
> > Tegra186 and later.
> >
> > Acked-by: Stephen Boyd <sboyd@xxxxxxxxxx>
> > Signed-off-by: Thierry Reding <treding@xxxxxxxxxx>
>
> There was already a bisection last Thursday which found this
> commit, and Thierry explained that it works in linux-next thanks
> to other patches. I guess those patches are not going to be
> cherry-picked onto the clk-next branch, so this will keep failing
> until it's rebased. Is that right?
>
> If so, I can turn off bisections on clk-next for now. We need to
> have a way in KernelCI to tell that a commit has been fixed to
> cope with this kind of situation in general.
>

I guess so. It's disappointing that a bisection hole was introduced
though. I can possibly merge something onto clk-next from the Tegra tree
to make this go away but the bisection hole will always exist. Or we can
all wait a week and not care about this problem anymore.