From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 41cMkl1jyBzDqkJ for ; Fri, 27 Jul 2018 18:36:24 +1000 (AEST) Date: Fri, 27 Jul 2018 10:36:19 +0200 From: Greg KH To: Stephen Rothwell Cc: Michael Ellerman , Benjamin Herrenschmidt , PowerPC , Linux-Next Mailing List , Linux Kernel Mailing List , Stefan Popa , Jonathan Cameron , Michael Hanselmann Subject: Re: linux-next: manual merge of the staging tree with the powerpc tree Message-ID: <20180727083619.GA17942@kroah.com> References: <20180727175911.76ed6d44@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20180727175911.76ed6d44@canb.auug.org.au> List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, Jul 27, 2018 at 05:59:11PM +1000, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the staging tree got a conflict in: > > MAINTAINERS > > between commit: > > d69ccc00c497 ("MAINTAINERS: Remove the entry for the orphaned ams driver") > > from the powerpc tree and commit: > > 28d1a7ac2a0d ("iio: dac: Add AD5758 support") > > from the staging 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. Looks good to me, thanks! greg k-h