On 05/02/2016 05:10 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.4.9 release. There are 163 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:04:47 UTC 2016. Anything received after that time might be too late.
Build results: total: 146 pass: 143 fail: 3 Failed builds: arm:allmodconfig arm64:allmodconfig mips:allmodconfig Qemu test results: total: 100 pass: 90 fail: 10 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 Details are available at http://kerneltests.org/builders. The failures are all build failures. 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' Culprit is "spi: rockchip: modify DMA max burst to 1". That patch would also require commit 6d5bbed30f89 ("dmaengine: core: expose max burst capability to clients"), which unfortunately does not apply cleanly. 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