From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751568AbcFUNCf (ORCPT ); Tue, 21 Jun 2016 09:02:35 -0400 Received: from 8bytes.org ([81.169.241.247]:54089 "EHLO theia.8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751260AbcFUNCd (ORCPT ); Tue, 21 Jun 2016 09:02:33 -0400 Date: Tue, 21 Jun 2016 14:54:35 +0200 From: Joerg Roedel To: Tomasz Figa Cc: "open list:IOMMU DRIVERS" , dri-devel , "linux-arm-kernel@lists.infradead.org" , "open list:ARM/Rockchip SoC..." , "linux-kernel@vger.kernel.org" , David Airlie , Heiko Stuebner , Mark Yao , Shunqian Zheng , Daniel Kurtz , Marek Szyprowski Subject: Re: [PATCH v4 0/8] iommu/rockchip: Fix bugs and enable on ARM64 Message-ID: <20160621125435.GE11432@8bytes.org> References: <1466483681-36110-1-git-send-email-tfiga@chromium.org> <20160621091732.GB28248@8bytes.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Thanks, Joerg