[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2015742.xhx642kbrC@diego>
Date: Tue, 21 Jun 2016 15:18:49 +0200
From: Heiko Stübner <heiko@...ech.de>
To: Joerg Roedel <joro@...tes.org>
Cc: Tomasz Figa <tfiga@...omium.org>,
"open list:IOMMU DRIVERS" <iommu@...ts.linux-foundation.org>,
dri-devel <dri-devel@...ts.freedesktop.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
David Airlie <airlied@...ux.ie>,
Mark Yao <mark.yao@...k-chips.com>,
Shunqian Zheng <zhengsq@...k-chips.com>,
Daniel Kurtz <djkurtz@...omium.org>,
Marek Szyprowski <m.szyprowski@...sung.com>
Subject: Re: [PATCH v4 0/8] iommu/rockchip: Fix bugs and enable on ARM64
Am Dienstag, 21. Juni 2016, 14:54:35 schrieb Joerg Roedel:
> Hi Tomasz,
>
> On Tue, Jun 21, 2016 at 09:42:16PM +0900, Tomasz Figa wrote:
> > In simple words, DRM patches depend on IOMMU patches.
> >
> > More precisely: The IOMMU patches alone are supposed to not break
> > anything. Same goes for the first DRM patch (7/8). Only second DRM
> > patch (8/8) depends on changes introduced by its predecessors.
>
> The first DRM patch is 6/7, so it is 7/8 with the iommu dependency,
> right? Anyway, I think the best is I take the iommu patches when Heiko
> is ok with them and then the DRM tree can merge that branch in to apply
> the DRM patches.
>
> But first Heiko should have a look at the patches.
I think from all his previous work on the rockchip iommus Tomasz is a lot more
qualified to judge them - which I guess he did when picking up the ones from
Rockchip devs :-) .
>From a style-side, please don't carry the Reviewed-on gerrit tags over to
mainline patches (patches 1 and 2).
Other than that, I didn't see anything jump out and it looks all pretty nice.
Heiko
Powered by blists - more mailing lists