From: Detlev Zundel <dzu@denx.de>
To: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/2] powerpc: export ppc_tb_freq so that modules can reference it
Date: Tue, 21 Sep 2010 14:34:58 +0200 [thread overview]
Message-ID: <m2d3s7w9zh.fsf@ohwell.denx.de> (raw)
In-Reply-To: 20100920135136.04ceb772__36164.799918379$1285008751$gmane$org@udp111988uds.am.freescale.net
Hi Scott,
> On Sat, 18 Sep 2010 14:22:12 -0400
> Josh Boyer <jwboyer@gmail.com> wrote:
>
>> Capitalizing? The patch you posted that uses this symbol is for a GPL
>> driver so you gain or lose nothing by having this symbol be
>> EXPORT_SYMBOL_GPL. Are you somehow advocating and getting some sort
>> of gain by allowing non-GPL modules? If so, I find that unfortunate.
>> If not, then I guess I don't understand what you mean by capitalizing.
>
> One can dislike DRM (even a very weak form such as this) without having
> a particular desire to go outside the bounds of what it allows.
>
> I thought EXPORT_SYMBOL_GPL was originally meant to indicate the
> symbols whose use is likely to be indicitave of code that is, in some
> copyright-meaningful way, derived from GPL code?
Google finds this, which coincides with what I remmber[1]:
EXPORT_SYMBOL_GPL
Some kernel developers are unhappy with providing external interfaces to
their code, only to see those interfaces being used by binary only
modules. They view it as their work being appropriated. Whether you
agree with that view or not is completely irrelevant, the person who
owns the copyright decides how their work can be used.
EXPORT_SYMBOL_GPL() allows for new interfaces to be marked as only
available to modules with a GPL compatible license. This is independent
of the kernel tainting, but obviously takes advantage of
MODULE_LICENSE() strings.
EXPORT_SYMBOL_GPL() may only be used for new exported symbols, Linus has
spoken. I believe the phrase involved killer penguins with chainsaws for
anybody who changed existing exported interfaces.
Cheers
Detlev
[1] http://lkml.indiana.edu/hypermail/linux/kernel/0110.2/0369.html
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu@denx.de
next prev parent reply other threads:[~2010-09-21 12:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 22:53 [PATCH 1/2] powerpc: export ppc_tb_freq so that modules can reference it Timur Tabi
2010-09-17 22:53 ` [PATCH 2/2] powerpc/watchdog: allow the e500 watchdog driver to be compiled as a module Timur Tabi
2010-09-18 0:37 ` Josh Boyer
2010-09-20 15:51 ` Timur Tabi
2010-09-20 19:30 ` Josh Boyer
2010-09-20 19:53 ` Timur Tabi
2010-09-18 0:38 ` [PATCH 1/2] powerpc: export ppc_tb_freq so that modules can reference it Josh Boyer
2010-09-18 1:20 ` Timur Tabi
2010-09-18 3:14 ` Benjamin Herrenschmidt
2010-09-18 14:36 ` Tabi Timur-B04825
2010-09-18 15:34 ` Kumar Gala
2010-09-18 15:52 ` Vitaly Wool
2010-09-18 16:56 ` Josh Boyer
2010-09-18 17:36 ` Tabi Timur-B04825
2010-09-18 17:46 ` Josh Boyer
2010-09-18 17:55 ` Tabi Timur-B04825
2010-09-18 18:22 ` Josh Boyer
2010-09-20 18:51 ` Scott Wood
[not found] ` <20100920135136.04ceb772__36164.799918379$1285008751$gmane$org@udp111988uds.am.freescale.net>
2010-09-21 12:34 ` Detlev Zundel [this message]
2010-09-18 18:36 ` Kumar Gala
2010-09-19 2:42 ` Benjamin Herrenschmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2d3s7w9zh.fsf@ohwell.denx.de \
--to=dzu@denx.de \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).