On 05/03/2016 11:21 AM, Greg Kroah-Hartman wrote:
On Tue, May 03, 2016 at 12:39:51AM -0700, Guenter Roeck wrote:
On 05/02/2016 05:09 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.5.3 release.
There are 200 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 Thu May 5 00:05:29 UTC 2016.
Anything received after that time might be too late.
Build results:
total: 147 pass: 144 fail: 3
Failed builds:
arm:allmodconfig
arm64:allmodconfig
mips:allmodconfig
Qemu test results:
total: 107 pass: 90 fail: 17
Failed tests:
arm:beagle:multi_v7_defconfig:omap3-beagle
arm:beaglexm:multi_v7_defconfig:omap3-beagle-xm
arm:overo:multi_v7_defconfig:omap3-overo-tobi
arm:vexpress-a9:multi_v7_defconfig:vexpress-v2p-ca9
arm:vexpress-a15:multi_v7_defconfig:vexpress-v2p-ca15-tc1
arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zc702
arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zc706
arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zed
arm:midway:multi_v7_defconfig:ecx-2000
arm:smdkc210:multi_v7_defconfig:exynos4210-smdkv310
arm:akita:pxa_defconfig
arm:borzoi:pxa_defconfig
arm:mainstone:pxa_defconfig
arm:spitz:pxa_defconfig
arm:terrier:pxa_defconfig
arm:tosa:pxa_defconfig
arm:z2:pxa_defconfig
Details are available at http://kerneltests.org/builders.
Same problem as with 4.4.
drivers/spi/spi-rockchip.c: In function 'rockchip_spi_prepare_dma':
drivers/spi/spi-rockchip.c:458:19: error: 'struct dma_slave_caps' has no member named 'max_burst'
drivers/spi/spi-rockchip.c:478:19: error: 'struct dma_slave_caps' has no member named 'max_burst'
As with 4.4, this is caused by "spi: rockchip: modify DMA max burst to 1".
Commit 6d5bbed30f89 ("dmaengine: core: expose max burst capability
to clients") does apply here and fixes the build problem.
I've now deleted this patch, thanks for letting me know.
Both 4.4 and 4.5 are now clean - all build and qemu tests pass.
Guenter
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html