On Sat, May 04, 2019 at 08:31:36PM -0700, Guenter Roeck wrote:
On 5/4/19 8:05 PM, Dan Rue wrote:
On Sat, May 04, 2019 at 12:24:45PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.0.13 release. There are 32 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.
Responses should be made by Mon 06 May 2019 10:24:23 AM UTC. Anything received after that time might be too late.
Results from Linaro’s test farm. Regressions detected.
Confusing. What are the regressions ? Below it says that there are none.
My mistake for dashing it off too quickly. No regressions on arm64, arm, x86_64, and i386.
Dan
Guenter
Summary
kernel: 5.0.13-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-5.0.y git commit: c6bd3efdcefd68cc590853c50594a9fc971d93cd git describe: v5.0.12-33-gc6bd3efdcefd Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-5.0-oe/build/v5.0.12-33-g...
No regressions (compared to build v5.0.11-102-g17f93022a8c9)
No fixes (compared to build v5.0.11-102-g17f93022a8c9)
Ran 25060 total tests in the following environments and test suites.
Environments
- dragonboard-410c
- hi6220-hikey
- i386
- juno-r2
- qemu_arm
- qemu_arm64
- qemu_i386
- qemu_x86_64
- x15
- x86
Test Suites
- build
- install-android-platform-tools-r2600
- kselftest
- libgpiod
- libhugetlbfs
- ltp-cap_bounds-tests
- ltp-commands-tests
- ltp-containers-tests
- ltp-cpuhotplug-tests
- ltp-cve-tests
- ltp-dio-tests
- ltp-fcntl-locktests-tests
- ltp-filecaps-tests
- ltp-fs_bind-tests
- ltp-fs_perms_simple-tests
- ltp-fsx-tests
- ltp-hugetlb-tests
- ltp-io-tests
- ltp-ipc-tests
- ltp-math-tests
- ltp-mm-tests
- ltp-nptl-tests
- ltp-pty-tests
- ltp-sched-tests
- ltp-securebits-tests
- ltp-syscalls-tests
- ltp-timers-tests
- perf
- spectre-meltdown-checker-test
- v4l2-compliance
- kvm-unit-tests
- ltp-fs-tests
- ltp-open-posix-tests
- kselftest-vsyscall-mode-native
- kselftest-vsyscall-mode-none