Re: [PATCH 4.0 00/55] 4.0.8-stable review
From: Kevin Hilman
Date: Fri Jul 10 2015 - 12:05:16 EST
Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> writes:
> This is the start of the stable review cycle for the 4.0.8 release.
> There are 55 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
Results from kernelci.org below.
Short version: PASS
Long version: while there are some boot failures, none of these are new
failures. I've just submitted a backport patch for v4.0.y to fix the
OMAP THUMB2_KERNEL=y failures, and the exynos5 failures are due to
missing NFS support which didn't hit upstream until v4.1. The NFSroot
tests will be removed from subsequent tests for v4.0.y
Kevin
stable-queue boot: 364 boots: 9 failed, 354 passed with 1 offline (v4.0.7-55-g279a3342322b)
Full Boot Summary: http://kernelci.org/boot/all/job/stable-queue/kernel/v4.0.7-55-g279a3342322b/
Full Build Summary: http://kernelci.org/build/stable-queue/kernel/v4.0.7-55-g279a3342322b/
Tree: stable-queue
Branch: local/linux-4.0.y-queue
Git Describe: v4.0.7-55-g279a3342322b
Git Commit: 279a3342322b9418c703e39b8418e0b925d0f508
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-stable.git
Tested: 96 unique boards, 22 SoC families, 28 builds out of 134
Boot Failures Detected: http://kernelci.org/boot/?v4.0.7-55-g279a3342322b&fail
arm:
multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y:
omap3-beagle: 1 failed lab
omap3-beagle-xm: 2 failed labs
omap3-n900: 1 failed lab
omap3-overo-storm-tobi: 1 failed lab
omap3-overo-tobi: 1 failed lab
exynos_defconfig:
exynos5422-odroidxu3_rootfs:nfs: 2 failed labs
exynos5800-peach-pi_rootfs:nfs: 1 failed lab
Offline Platforms:
arm:
omap2plus_defconfig:
am335x-boneblack: 1 offline lab
---
For more info write to <info@xxxxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/