Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752039AbdGERUW (ORCPT ); Wed, 5 Jul 2017 13:20:22 -0400 Received: from verein.lst.de ([213.95.11.211]:55573 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751992AbdGERUV (ORCPT ); Wed, 5 Jul 2017 13:20:21 -0400 Date: Wed, 5 Jul 2017 19:20:19 +0200 From: Christoph Hellwig To: Tomasz Figa Cc: Christoph Hellwig , "open list:IOMMU DRIVERS" , "linux-kernel@vger.kernel.org" , Marek Szyprowski , Robin Murphy , Greg Kroah-Hartman , Joerg Roedel , Will Deacon , Vineet Gupta , Hans-Christian Noren Egtvedt , Mitchel Humpherys , Krzysztof Kozlowski , Arnd Bergmann Subject: Re: [RFC PATCH 1/5] base: dma-mapping: Export commonly used symbols Message-ID: <20170705172019.GB5246@lst.de> References: <20170705071215.17603-1-tfiga@chromium.org> <20170705071215.17603-2-tfiga@chromium.org> <20170705151728.GA2479@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: 733 Lines: 13 On Thu, Jul 06, 2017 at 12:22:35AM +0900, Tomasz Figa wrote: > Generally the user is a work in progress that should be posted in a > very near future. You can find a reference to our downstream tree at > chromium.org in the cover letter. Obviously I don't mind including > patches from this series in the driver series later and that's one of > the reasons for this series being RFC. Please post and explain them here. In general I think moving dma ops and iommu implementations into modules is a bad idea, but I don't want to reject the idea before seeing the code. Or maybe by looking at the user we can come up with an even better idea to solve the original issue you're trying to solve, so please also explain your rationale.