next-20160225 build: 2 failures 44 warnings (next-20160225)
From: broonie@kernel.org (Mark Brown)
Date: 2016-02-26 03:09:49
Also in:
linux-next, linux-watchdog
Possibly related (same subject, not in this thread)
- 2016-02-26 · next-20160225 build: 2 failures 44 warnings (next-20160225) · bhelgaas@google.com (Bjorn Helgaas)
- 2016-02-26 · next-20160225 build: 2 failures 44 warnings (next-20160225) · Thomas Petazzoni <hidden>
- 2016-02-26 · next-20160225 build: 2 failures 44 warnings (next-20160225) · broonie@kernel.org (Mark Brown)
On Thu, Feb 25, 2016 at 10:04:29AM +0000, Build bot for Mark Brown wrote: Today's -next fails to build an arm64 allmodconfig due to:
arm64-allmodconfig ../drivers/watchdog/orion_wdt.c:109:2: error: implicit declaration of function 'atomic_io_modify' [-Werror=implicit-function-declaration]
also caused by b4f596b19624 (arm64: add mvebu architecture entry) which enables MVBEU on arm64, the commit was present for a little while and the error cropped up but didn't get reported due to other things masking it. atomic_io_modify() is only available on ARM, I'm unsure if this needs a driver change or if the driver is just specific to older hardware anyway. The code is only used in the init path accessing what look to be device specific registers so I'm not 100% clear why it specifically needs to be an atomic modify. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160226/23d7bd97/attachment.sig>