On Fri, 20 Mar 2020 at 13:41, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Fri, Mar 20, 2020 at 09:03:17AM +0100, Greg Kroah-Hartman wrote:
On Thu, Mar 19, 2020 at 08:00:32PM +0000, Ben Hutchings wrote:
On Fri, 2020-03-20 at 01:12 +0530, Naresh Kamboju wrote:
On Thu, 19 Mar 2020 at 18:50, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 4.19.112 release. There are 48 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 Sat, 21 Mar 2020 12:37:04 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at: https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.112-rc... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.19.y and the diffstat can be found below.
thanks,
greg k-h
Faiz Abbas faiz_abbas@ti.com mmc: sdhci-omap: Fix Tuning procedure for temperatures < -20C
Faiz Abbas faiz_abbas@ti.com mmc: sdhci-omap: Don't finish_mrq() on a command error during tuning
Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386.
NOTE: The arm beagleboard x15 device running stable rc 4.19.112-rc1, 5.4.27-rc1 and 5.5.11-rc2 kernel pops up the following messages on console log, Is this a problem ?
[ 15.737765] mmc1: unspecified timeout for CMD6 - use generic [ 16.754248] mmc1: unspecified timeout for CMD6 - use generic [ 16.842071] mmc1: unspecified timeout for CMD6 - use generic ... [ 977.126652] mmc1: unspecified timeout for CMD6 - use generic [ 985.449798] mmc1: unspecified timeout for CMD6 - use generic
[...]
This warning was introduced by commit 533a6cfe08f9 "mmc: core: Default to generic_cmd6_time as timeout in __mmc_switch()". That should not be applied to stable branches; it is not valid without (at least) these preparatory changes:
0c204979c691 mmc: core: Cleanup BKOPS support 24ed3bd01d6a mmc: core: Specify timeouts for BKOPS and CACHE_FLUSH for eMMC ad91619aa9d7 mmc: block: Use generic_cmd6_time when modifying INAND_CMD38_ARG_EXT_CSD
Ok, I've now dropped that patch, which also required me to drop 1292e3efb149 ("mmc: core: Allow host controllers to require R1B for CMD6"). I've done so for 5.5.y, 5.4.y, and 4.19.y.
Ugh, I forgot, that broke other things. I'm going to go rip out a bunch of mmc patches now...
[Am i missing rc2 tag ?]
Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386.
Summary ------------------------------------------------------------------------
kernel: 4.19.112-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.19.y git commit: d078cac7a42286ba7c97801a763fc42ad7baf5c1 git describe: v4.19.109-136-gd078cac7a422 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.19-oe/build/v4.19.109-1...
No regressions (compared to build v4.19.109)
No fixes (compared to build v4.19.109)
Ran 23963 total tests in the following environments and test suites.
Environments -------------- - dragonboard-410c - arm64 - hi6220-hikey - i386 - juno-r2 - arm64 - juno-r2-compat - juno-r2-kasan - nxp-ls2088 - x15 - x86_64 - x86-kasan - qemu_arm - qemu_arm64 - qemu_i386 - qemu_x86_64
Test Suites ----------- * install-android-platform-tools-r2800 * linux-log-parser * ltp-ipc-tests * v4l2-compliance * kvm-unit-tests * libhugetlbfs * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-cpuhotplug-tests * ltp-crypto-tests * ltp-cve-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests