On Sun, May 05, 2019 at 11:02:36AM +0200, Greg Kroah-Hartman wrote: > On Sun, May 05, 2019 at 02:23:22PM +0530, Naresh Kamboju wrote: > > On Sun, 5 May 2019 at 12:38, Greg Kroah-Hartman > > <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > > > On Sat, May 04, 2019 at 10:00:44PM -0500, Dan Rue wrote: > > > > On Sat, May 04, 2019 at 12:25:02PM +0200, Greg Kroah-Hartman wrote: > > > > > This is the start of the stable review cycle for the 4.19.40 release. > > > > > There are 23 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:19 AM UTC. > > > > > Anything received after that time might be too late. > > > > > > > > > > > > Results from Linaro’s test farm. > > > > Regressions detected. > > > > > > Really? Where? > > > > Not really. > > selftest: net: msg_zerocopy.sh is an intermittent failure on qemu_i386 device. > > Is that a test problem, or a qemu problem? > > > We could ignore this failure as known issues. > > It wasn't listed in the report, or did I miss it? It needs further investigation, but it's unrelated to this RC. It's an intermittent failure that we see sometimes but only ever on qemu. With the amount of tests that we run, this is common - our process is to investigate the failure and determine if the failure is a regression or not. In this case, I determined that it was not a real regression, but I did not run the right command to generate the report accordingly. No regressions on arm64, arm, x86_64, and i386. Dan
