From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joerg Roedel Subject: Re: next-20160707 build: 1 failures 6 warnings (next-20160707) Date: Thu, 7 Jul 2016 17:32:37 +0200 Message-ID: <20160707153237.GF11467@suse.de> References: <20160707122219.GO6247@sirena.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "Linux-rockchip" Errors-To: linux-rockchip-bounces+glpar-linux-rockchip=m.gmane.org-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org To: Tomasz Figa Cc: linaro-kernel-cunTk1MwBs8s++Sfvej+rw@public.gmane.org, Simon Xue , kernel-build-reports-cunTk1MwBs8s++Sfvej+rw@public.gmane.org, David Airlie , dri-devel , "open list:ARM/Rockchip SoC..." , Mark Brown , linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Mark Yao , Shunqian Zheng , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" , Heiko Stuebner List-Id: linux-rockchip.vger.kernel.org On Thu, Jul 07, 2016 at 10:18:02PM +0900, Tomasz Figa wrote: > This is probably because we missed this hidden dependency and decided > to push the IOMMU part separately through the IOMMU tree. I guess we > can remove the offending patch from the IOMMU tree and let the DRM > tree include it based on a topic branch from Joerg. > > Joerg, David, Mark Yao, what do you think? Will the DRM patches go upstream soon, or is there still discussion around them? For now I am going to remove/revert that patch in my tree. Joerg