From: Josh Boyer <jwboyer@gmail.com>
To: Tabi Timur-B04825 <B04825@freescale.com>
Cc: linuxppc-dev@ozlabs.org,
Gala Kumar-B11780 <kumar.gala@freescale.com>,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 1/2] powerpc: export ppc_tb_freq so that modules can reference it
Date: Sat, 18 Sep 2010 13:46:21 -0400 [thread overview]
Message-ID: <AANLkTimSewEEhbBoBb+fpPgY9EbE5bWsknPS7OkQgkcy@mail.gmail.com> (raw)
In-Reply-To: <5610599F537DD74A8D1F5CC946A75073034792F7@az33exm25.fsl.freescale.net>
On Sat, Sep 18, 2010 at 1:36 PM, Tabi Timur-B04825 <B04825@freescale.com> w=
rote:
> Josh Boyer wrote:
>> It is not, in my opinion, about what is technically possible and what
>> isn't.=A0 The kernel is licensed under the GPL.=A0 This is a Linux kerne=
l
>> only symbol.=A0 One would be hard pressed to claim they have a driver
>> that wasn't written for Linux that happens to need that symbol.=A0 As a
>> member of the Linux kernel community, I find it important to encourage
>> the contribution of code back to the kernel, and this is one way to
>> help that.=A0 This isn't BSD.
>
> Fine, but this goes back to my original question -- if this is how the
> community feels, then why hasn't someone posted a patch that converts all
> EXPORT_SYMBOL into EXPORT_SYMBOL_GPL?
Because of history in a lot of cases, and like all communities,
opinions vary. I did say this was my opinion, not a mandate of some
sort.
> Either we allow non-GPL drivers, or we don't.=A0 If we don't, then we nee=
d to
> eliminate EXPORT_SYMBOL once and for all.=A0 Otherwise, the message is
> hypocritical.
I'd be all for it. I don't think it is as black and white as that
though, as nothing rarely is. (we can't even get all the code to
adhere to the < 80 column "rule" ). I also don't think it is
necessarily hypocritical. This is a new symbol being exported, not
one that has been exported for years.
josh
next prev parent reply other threads:[~2010-09-18 17:46 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 [this message]
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
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=AANLkTimSewEEhbBoBb+fpPgY9EbE5bWsknPS7OkQgkcy@mail.gmail.com \
--to=jwboyer@gmail.com \
--cc=B04825@freescale.com \
--cc=kumar.gala@freescale.com \
--cc=linux-watchdog@vger.kernel.org \
--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).