On Monday 15 December 2014 15:54:42 Mark Brown wrote:
The Exynos IOMMU driver uses the ARM specific dmac_flush_range() and
outer_flush_range() functions. This breaks the build on arm64 allmodconfig
in -next since support has been merged for some Exynos ARMv8 SoCs. Add a
dependency on ARM to
On 15.12.2014 14:00, Mark Brown wrote:
The Exynos IOMMU driver uses the ARM specific dmac_flush_range() and
outer_flush_range() functions. This breaks the build on arm64 allmodconfig
in -next since support has been merged for some Exynos ARMv8 SoCs. Add a
dependency on ARM to keep things
On Mon, Dec 15, 2014 at 02:10:37PM +0100, Krzysztof Kozłowski wrote:
Hi Mark,
Few days ago I posted similar patch:
https://lkml.org/lkml/2014/12/5/268
but no one have picked it up.
Anyway the fix of yours seems fine to me.
I don't mind either way, it just seemed to be easier to report the
On Mon, Dec 15, 2014 at 03:35:29PM +, Mark Brown wrote:
On Mon, Dec 15, 2014 at 02:10:37PM +0100, Krzysztof Kozłowski wrote:
Few days ago I posted similar patch:
https://lkml.org/lkml/2014/12/5/268
but no one have picked it up.
Anyway the fix of yours seems fine to me.
I don't
The Exynos IOMMU driver uses the ARM specific dmac_flush_range() and
outer_flush_range() functions. This breaks the build on arm64 allmodconfig
in -next since support has been merged for some Exynos ARMv8 SoCs. Add a
dependency on ARM to keep things building until either the driver has the
ARM
On Mon, Dec 15, 2014 at 03:38:04PM +, Will Deacon wrote:
On Mon, Dec 15, 2014 at 03:35:29PM +, Mark Brown wrote:
I don't mind either way, it just seemed to be easier to report the bug
with a patch. If Jeorg is busy perhaps it can go via the arm64 tree,
the issue is triggered by
