On Fri, Feb 9, 2018 at 11:36 AM, kernelci.org bot <bot@xxxxxxxxxxxx> wrote: > stable-rc/linux-4.14.y boot: 111 boots: 2 failed, 109 passed (v4.14.18-23-g8d861f5b27b0) > > Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.18-23-g8d861f5b27b0/ > Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.14.y/kernel/v4.14.18-23-g8d861f5b27b0/ > > Tree: stable-rc > Branch: linux-4.14.y > Git Describe: v4.14.18-23-g8d861f5b27b0 > Git Commit: 8d861f5b27b05466ce2a9d3c4108367555dccefe > Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > Tested: 63 unique boards, 22 SoC families, 16 builds out of 185 TL;DR; All is well. > Boot Regressions Detected: > > arm64: > > defconfig: > bcm2837-rpi-3-b: > lab-baylibre: new failure (last pass: v4.14.18-19-g44b8fc264b98) > r8a7795-salvator-x: > lab-baylibre: new failure (last pass: v4.14.18-19-g44b8fc264b98) Both of these are a bootloader failure to TFTP a kernel image. Kevin