On Mon, Jun 12, 2017 at 12:59 PM, kernelci.org bot <bot@xxxxxxxxxxxx> wrote:
> stable-rc/linux-4.4.y build: 199 builds: 13 failed, 186 passed, 13 errors, 4 warnings (v4.4.71-63-g409ebd600970)
>
>
> arm: gcc version 5.3.1 20160412 (Linaro GCC 5.3-2016.05)
>
> ep93xx_defconfig: 1 error
>
> mips: gcc version 6.3.0 (GCC)
>
> decstation_defconfig: 1 error
> defconfig+CONFIG_LKDTM=y: 1 error
> ip22_defconfig: 1 error
> jazz_defconfig: 1 error
> malta_defconfig: 1 error
> malta_kvm_defconfig: 1 error
> malta_kvm_guest_defconfig: 1 error
> maltaup_xpa_defconfig: 1 error
> nlm_xlp_defconfig: 1 error
> nlm_xlr_defconfig: 1 error
> rm200_defconfig: 1 error
>
> Errors summary:
>
> 12 fs/ufs/balloc.c:501:26: error: implicit declaration of function 'i_blocksize' [-Werror=implicit-function-declaration]
Same as stable-rc/linux-4.9.y, this needs a backport of 93407472a21b ("fs: add
i_blocksize()")
> 1 drivers/dma/ep93xx_dma.c:1357:9: error: 'struct dma_device' has no member named 'device_synchronize'
The error was introudced by the backport of 98f9de366fcc ("dmaengine: ep93xx:
Don't drain the transfers in terminate_all()"), which requires the dmaengine
synchronize callback.
device_synchronize was introduced by b36f09c3c441 ("dmaengine: Add transfer
termination synchronization support") in linux-4.5. That is not a
bugfix but would
cleanly apply on top of 4.4 and has no dependencies or side-effects.
We can either revert 98f9de366fcc or backport b36f09c3c441.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe dmaengine" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
