Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751941AbdGEPXB (ORCPT ); Wed, 5 Jul 2017 11:23:01 -0400 Received: from mail-yb0-f182.google.com ([209.85.213.182]:36706 "EHLO mail-yb0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751886AbdGEPW6 (ORCPT ); Wed, 5 Jul 2017 11:22:58 -0400 MIME-Version: 1.0 In-Reply-To: <20170705151728.GA2479@lst.de> References: <20170705071215.17603-1-tfiga@chromium.org> <20170705071215.17603-2-tfiga@chromium.org> <20170705151728.GA2479@lst.de> From: Tomasz Figa Date: Thu, 6 Jul 2017 00:22:35 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [RFC PATCH 1/5] base: dma-mapping: Export commonly used symbols To: Christoph Hellwig Cc: "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 Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1178 Lines: 29 Hi Christoph, Thanks for comments! On Thu, Jul 6, 2017 at 12:17 AM, Christoph Hellwig wrote: > Please use EXPORT_SYMBOL_GPL for any of these exports, as they are > internal linux implementration details by any definition of it. Right. I typically lean towards EXPORT_SYMBOL_GPL(), but was misled by existing EXPORT_SYMBOL()s in the file. Will fix. > > On Wed, Jul 05, 2017 at 04:12:11PM +0900, Tomasz Figa wrote: >> There is nothing wrong in having a loadable module implementing DMA API, >> for example to be used for sub-devices registered by the module. >> However, most of the functions from dma-mapping do not have their >> symbols exported, making it impossible to use them from loadable modules. > > I'd like to see the patches for this use case as well. We don't > generally export symbols without seeing the users. 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. Best regards, Tomasz