From: David Woodhouse <dwmw2@infradead.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: David Howells <dhowells@redhat.com>,
torvalds@osdl.org, akpm@osdl.org,
Michael C Thompson <mcthomps@us.ibm.com>,
keyrings@linux-nfs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Keys: Export user-defined keyring operations
Date: Wed, 05 Oct 2005 14:32:58 +0100 [thread overview]
Message-ID: <1128519178.3116.16.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <1128510159.2920.15.camel@laptopd505.fenrus.org>
On Wed, 2005-10-05 at 13:02 +0200, Arjan van de Ven wrote:
> since this is new unique-to-linux functionality, could you please
> consider making the exports _GPL please?
What's the point? There can be no difference between the meaning of
EXPORT_SYMBOL() and EXPORT_SYMBOL_GPL() anyway.
§6 of the GPL says "You may not impose any further restrictions on the
recipients' exercise of the rights granted herein."
If there was really a meaningful difference between EXPORT_SYMBOL_GPL()
and EXPORT_SYMBOL(), then the GPL _itself_ would forbid the use of
EXPORT_SYMBOL_GPL() within the kernel, because that would impose
additional restrictions.
We should abolish the meaningless distinction between the two, because
it only encourages people to believe that EXPORT_SYMBOL() can be used
for non-GPL code. Either use EXPORT_SYMBOL() for everything, or switch
to EXPORT_SYMBOL_GPL() for everything. It doesn't really matter.
--
dwmw2
next prev parent reply other threads:[~2005-10-05 13:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF7208B0E9.0AB77A04-ON87257090.007A1D4E-05257090.007A2207@us.ibm.com>
2005-10-05 10:58 ` David Howells
2005-10-05 11:02 ` Arjan van de Ven
2005-10-05 13:32 ` David Woodhouse [this message]
2005-10-05 14:50 ` Linus Torvalds
2005-10-05 11:40 ` David Howells
2005-10-05 12:00 ` Arjan van de Ven
2005-10-05 12:06 ` David Howells
2005-10-05 12:11 ` Arjan van de Ven
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=1128519178.3116.16.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=dhowells@redhat.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcthomps@us.ibm.com \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®