From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752002Ab3CAQa1 (ORCPT ); Fri, 1 Mar 2013 11:30:27 -0500 Received: from mail-bk0-f41.google.com ([209.85.214.41]:49700 "EHLO mail-bk0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750778Ab3CAQaY (ORCPT ); Fri, 1 Mar 2013 11:30:24 -0500 MIME-Version: 1.0 In-Reply-To: <20130301135529.GB27373@kroah.com> References: <1362098606-26469-1-git-send-email-john.stultz@linaro.org> <1362098606-26469-11-git-send-email-john.stultz@linaro.org> <20130301020008.GB13367@kroah.com> <51302792.6040408@linaro.org> <20130301135529.GB27373@kroah.com> From: Erik Gilling Date: Fri, 1 Mar 2013 08:30:02 -0800 X-Google-Sender-Auth: Nu_qAaLyfCpiimuxweIwAbTsp4M Message-ID: Subject: Re: [PATCH 10/30] staging: sync: Export sync API symbols To: Greg KH Cc: John Stultz , lkml , Maarten Lankhorst , Daniel Vetter , Rob Clark , Sumit Semwal , dri-devel@lists.freedesktop.org, Android Kernel Team Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 1, 2013 at 5:55 AM, Greg KH wrote: > On Fri, Mar 01, 2013 at 12:21:24AM -0800, Erik Gilling wrote: >> As John pointed out, the exynos and msm display and code uses them. I >> know nvidia is working on adding suport to their tegra tree. My knee >> jerk reaction is to make the export as permissible as possible. That >> being said, all of the ARM SoC vendors I've worked with have GPL >> kernel drivers even if their user space is closed. I'll reach out to >> them and ask for their opinions. Are there any issues with keeping >> them EXPORT_SYMBOL? > > There's no "issues", it's just that it is preferred by some people and > companies to add new symbols to the kernel in this manner. It's really > up to you / Google as you are the ones contributing the code. Ok. Lets keep it EXPORT_SYMBOL then. Cheers, Erik