On Tue, 19 Mar 2019 at 01:38, Shawn Lin <shawn.lin@xxxxxxxxxxxxxx> wrote: > > > On 2019/3/19 6:50, 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. * > > * Hope this helps! * > > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * > > > > ulfh/next boot bisection: v5.1-rc1-22-gb3725d97ba75 on rk3399-gru-kevin > > > > Summary: > > Start: b3725d97ba75 Merge branch 'fixes' into next > > Details: https://kernelci.org/boot/id/5c8fa85d59b5148afcfe6052 > > Plain log: https://storage.kernelci.org//ulfh/next/v5.1-rc1-22-gb3725d97ba75/arm64/defconfig/gcc-7/lab-collabora/boot-rk3399-gru-kevin.txt > > HTML log: https://storage.kernelci.org//ulfh/next/v5.1-rc1-22-gb3725d97ba75/arm64/defconfig/gcc-7/lab-collabora/boot-rk3399-gru-kevin.html > > Result: d6a6d722481f mmc: dw_mmc-rockchip: Enable hardware unbusy interrupt support > > Thanks for report! > > Ulf, > > It's a known issue already but didn't got managed to post v3 due to > weekend. Should I post a increamental patch on top? or just resend a > v3 series? I have just dropped the offending patches (the series), please post a new version. [...] Kind regards Uffe
