Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756857AbbHZRlV (ORCPT ); Wed, 26 Aug 2015 13:41:21 -0400 Received: from verein.lst.de ([213.95.11.211]:41581 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752902AbbHZRlT (ORCPT ); Wed, 26 Aug 2015 13:41:19 -0400 Date: Wed, 26 Aug 2015 19:41:17 +0200 From: Christoph Hellwig To: Max Filippov Cc: Christoph Hellwig , Guenter Roeck , Chris Zankel , Andrew Morton , "linux-xtensa@linux-xtensa.org" , LKML Subject: Re: xtensa build failures in -next due to DMA API changes Message-ID: <20150826174117.GA16076@lst.de> References: <20150825200756.GA25409@roeck-us.net> <20150825201532.GA24940@lst.de> <20150825202140.GB25409@roeck-us.net> <20150825202439.GA25236@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Content-Length: 684 Lines: 14 On Wed, Aug 26, 2015 at 10:53:25AM +0300, Max Filippov wrote: > Looks like I just need to remove now redundant function definitions from > xtensa/include/asm/dma-mapping.h. A patch that removes these > functions is attached, but I'm not sure where it should go. To the Andrew's > tree? Or should the xtensa tree merge Christoph's series and apply it on > top? This looks fine to me. Thanks for converting xtensa to the generic DMA code! -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/