From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750985AbeFAHh0 (ORCPT ); Fri, 1 Jun 2018 03:37:26 -0400 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:39581 "EHLO out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750729AbeFAHhY (ORCPT ); Fri, 1 Jun 2018 03:37:24 -0400 X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Sender: Date: Fri, 1 Jun 2018 09:37:00 +0200 From: Greg KH To: Stephen Rothwell Cc: Christoph Hellwig , Linux-Next Mailing List , Linux Kernel Mailing List , Martin Liu Subject: Re: linux-next: manual merge of the driver-core tree with the dma-mapping tree Message-ID: <20180601073700.GA12809@kroah.com> References: <20180601170825.622c7084@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180601170825.622c7084@canb.auug.org.au> User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 01, 2018 at 05:08:25PM +1000, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the driver-core tree got a conflict in: > > include/linux/device.h > > between commit: > > 3d6ce86ee794 ("drivers: remove force dma flag from buses") > > from the dma-mapping tree and commit: > > 8c97a46af04b ("driver core: hold dev's parent lock when needed") > > from the driver-core tree. > > I fixed it up (see below) and can carry the fix as necessary. This > is now fixed as far as linux-next is concerned, but any non trivial > conflicts should be mentioned to your upstream maintainer when your tree > is submitted for merging. You may also want to consider cooperating > with the maintainer of the conflicting tree to minimise any particularly > complex conflicts. Fix looks great to me, thanks for this. greg k-h