Hi Joerg, Am Donnerstag, 27. Juli 2017, 14:15:18 CEST schrieb Joerg Roedel: > Hey Heiko, > > On Wed, Jul 26, 2017 at 03:53:06PM +0200, Heiko Stübner wrote: > > Having code and dts changes go through different trees is no problem, as > > they don't have a compile-time dependencies on each other and come > > together nicely in linux-next again. > > Okay, I removed > > ARM64: dts: rockchip: rk3328 add iommu nodes > ARM: dts: rockchip: rk322x add iommu nodes > ARM64: dts: rockchip: rk3368 add iommu nodes > ARM64: dts: rockchip: rk3399 add iommu nodes > ARM64: dts: rockchip: rk3328 add iommu nodes > ARM: dts: rockchip: rk322x add iommu nodes > ARM64: dts: rockchip: rk3368 add iommu nodes > ARM64: dts: rockchip: rk3399 add iommu nodes > > from my tree again and kept > > Docs: dt: rockchip: add rockchip,disable-mmu-reset property > iommu/rockchip: add multi irqs support > iommu/rockchip: ignore isp mmu reset operation great, thanks. Interestingly it seems you had the dts patches 2 times each likely from v1 and v2. But they're gone now, so all good :-) Heiko -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
