[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180925204723.GC13170@roeck-us.net>
Date: Tue, 25 Sep 2018 13:47:23 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, shuah@...nel.org, patches@...nelci.org,
ben.hutchings@...ethink.co.uk, lkft-triage@...ts.linaro.org,
stable@...r.kernel.org
Subject: Re: [PATCH 4.14 000/173] 4.14.72-stable review
On Mon, Sep 24, 2018 at 01:50:34PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.72 release.
> There are 173 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 Wed Sep 26 11:30:10 UTC 2018.
> Anything received after that time might be too late.
>
Build results:
total: 151 pass: 151 fail: 0
Qemu test results:
total: 315 pass: 312 fail: 3
Failed tests:
powerpc:g3beige:ppc_book3s_defconfig:nosmp:ide:rootfs
i386:pc:EPYC:defconfig:smp:efi32:scsi[MEGASAS]:rootfs
i386:pc:Westmere:defconfig:pae:smp:efi32:usb:rootfs
The failed powerpc test is the result of a crash in devicetree unittest code.
It affects all branches. Nothing to worry about; fix is being worked on.
The failed i386 qemu boot tests are spurious and happen during reboot;
the system shuts down early. This deserves some analysis, but is nothing
to worry about at this time.
Several of the qemu test results show runtime warnings not previously seen.
This is because I enabled various debug options. I'll analyze and report
those separately. This affects all releases.
Details are available at https://kerneltests.org/builders/.
Guenter
Powered by blists - more mailing lists