On 20/11/2019 05:25, kernelci.org bot wrote: > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * > * This automated bisection report was sent to you on the basis * > * that you may be involved with the breaking commit it has * > * found. No manual investigation has been done to verify it, * > * and the root cause of the problem may be somewhere else. * > * * > * If you do send a fix, please include this trailer: * > * Reported-by: "kernelci.org bot" <bot@xxxxxxxxxxxx> * > * * > * Hope this helps! * > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * > > clk/clk-next bisection: boot on tegra124-nyan-big > > Summary: > Start: cd89054e321a Merge branch 'clk-init-leak' into clk-next > Details: https://kernelci.org/boot/id/5dd486b059b514415acf54bd > Plain log: https://storage.kernelci.org//clk/clk-next/clk-fixes-for-linus-196-gcd89054e321a/arm/tegra_defconfig/gcc-8/lab-collabora/boot-tegra124-nyan-big.txt > HTML log: https://storage.kernelci.org//clk/clk-next/clk-fixes-for-linus-196-gcd89054e321a/arm/tegra_defconfig/gcc-8/lab-collabora/boot-tegra124-nyan-big.html > Result: 25175c806a68 clk: tegra: Reimplement SOR clock on Tegra124 > > Checks: > revert: PASS > verify: PASS > > Parameters: > Tree: clk > URL: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git > Branch: clk-next > Target: tegra124-nyan-big > CPU arch: arm > Lab: lab-collabora > Compiler: gcc-8 > Config: tegra_defconfig > Test suite: boot > > Breaking commit found: > > ------------------------------------------------------------------------------- > commit 25175c806a6841149abe46168e0af12593141612 > 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. Thanks, Guillaume
