From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932190AbeAQQSs (ORCPT ); Wed, 17 Jan 2018 11:18:48 -0500 Received: from verein.lst.de ([213.95.11.211]:56174 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753993AbeAQQSo (ORCPT ); Wed, 17 Jan 2018 11:18:44 -0500 Date: Wed, 17 Jan 2018 17:18:43 +0100 From: Christoph Hellwig To: Stephen Rothwell Cc: Jens Axboe , Christoph Hellwig , Linux-Next Mailing List , Linux Kernel Mailing List , Bart Van Assche Subject: Re: linux-next: manual merge of the block tree with the dma-mapping tree Message-ID: <20180117161843.GA14823@lst.de> References: <20180117133817.739d6751@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180117133817.739d6751@canb.auug.org.au> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 17, 2018 at 01:38:17PM +1100, Stephen Rothwell wrote: > from the dma-mapping tree and commit: > > e80a0af4759a ("lib/scatterlist: Introduce sgl_alloc() and sgl_free()") > > from the block 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. Thanks, the trivial fix look good.