From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Airlie Subject: Re: linux-next: build failure after merge of the drm tree Date: Wed, 20 May 2015 07:08:51 +0100 (IST) Message-ID: References: <20150520130828.4fdacf54@canb.auug.org.au> <20150520152538.15e7a1cc@canb.auug.org.au> <20150520153102.3e70a45c@canb.auug.org.au> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: Received: from gir.skynet.ie ([193.1.99.77]:59459 "EHLO gir.skynet.ie" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751532AbbETGI7 (ORCPT ); Wed, 20 May 2015 02:08:59 -0400 In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: Oded Gabbay Cc: Stephen Rothwell , linux-next@vger.kernel.org, "Linux-Kernel@Vger. Kernel. Org" , Alex Deucher > >> > drm-next and fix it up there. > >> > >> Yep, against commit 79b066bd76d5 ("drm/amdkfd: Initialize sdma vm when > >> creating sdma queue") which is in v4.1-rc3. > > > > So you could, of course, just merge that commit instead of Linus' > > tree ... > > > > -- > > Cheers, > > Stephen Rothwell sfr@canb.auug.org.au > > Hi, > Did I need to do something different in order to prevent this conflict ? > Do some manual merge before sending the pull request ? > Well this sort of thing is why linux-next exists, you can pull Linus's tree into yours to see if it builds before pulling, but you can find yourself fixing conflicts in other parts of the drm stack then. I'll pull v4.1-rc4 tag in as a nicer merge point that misc Linus master. Dave.