From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933923AbcIEN6H (ORCPT ); Mon, 5 Sep 2016 09:58:07 -0400 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:56907 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933512AbcIEN6D (ORCPT ); Mon, 5 Sep 2016 09:58:03 -0400 X-Sasl-enc: mXu1B2q3ICeUlKR6ZYcCxPdRe4k4l1dyw0Sj8OyvVA2H 1473083880 Date: Mon, 5 Sep 2016 15:55:41 +0200 From: Greg KH To: Vinod Koul Cc: Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Nandor Han , Dave Jiang Subject: Re: linux-next: manual merge of the tty tree with the slave-dma tree Message-ID: <20160905135541.GA13403@kroah.com> References: <20160905164321.4dd8801b@canb.auug.org.au> <20160905112802.GJ9355@localhost> <20160905113333.GA27586@kroah.com> <20160905124305.GQ9355@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160905124305.GQ9355@localhost> User-Agent: Mutt/1.7.0 (2016-08-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Sep 05, 2016 at 06:13:05PM +0530, Vinod Koul wrote: > On Mon, Sep 05, 2016 at 01:33:33PM +0200, Greg KH wrote: > > On Mon, Sep 05, 2016 at 04:58:02PM +0530, Vinod Koul wrote: > > > On Mon, Sep 05, 2016 at 04:43:21PM +1000, Stephen Rothwell wrote: > > > > Hi Greg, > > > > > > > > Today's linux-next merge of the tty tree got a conflict in: > > > > > > > > drivers/dma/imx-sdma.c > > > > > > > > between commit: > > > > > > > > 48dc77e2d4fc ("dmaengine: imx-sdma: convert callback to helper function") > > > > > > > > from the slave-dma tree and commit: > > > > > > > > 15f30f513111 ("dmaengine: imx-sdma - reduce transfer latency for DMA cyclic clients") > > > > > > > > from the tty 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. > > > > > > Stephen, > > > > > > The fix looks right to me. > > > > > > Greg let me know if you would like me to merge this to avoid conflict > > > > Sure, which way do you want to merge, do you want me to pull your tree > > into mine, or do you want to pull my tree into yours? Either is fine > > with me. > > Great, I would prefer to pull. Do you want a signed tag, or do you just want to pull my tty-next branch directly into your tree? thanks, greg k-h