From: Daniel Phillips <phillips@google.com>
To: Harald Welte <laforge@gnumonks.org>
Cc: bidulock@openss7.org, Stephen Hemminger <shemminger@osdl.org>,
Sridhar Samudrala <sri@us.ibm.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC/PATCH 1/2] in-kernel sockets API
Date: Wed, 14 Jun 2006 10:48:56 -0700 [thread overview]
Message-ID: <44904C08.6020307@google.com> (raw)
In-Reply-To: <20060614133022.GU11863@sunbeam.de.gnumonks.org>
Hi Harald,
You wrote:
> On Tue, Jun 13, 2006 at 02:12:41PM -0700, I wrote:
>
>>This has the makings of a nice stable internal kernel api. Why do we want
>>to provide this nice stable internal api to proprietary modules?
>
> because there is IMHO legally nothing we can do about it anyway.
Speaking as a former member of a "grey market" binary module vendor that
came in from the cold I can assure you that the distinction between EXPORT
and EXPORT_GPL _is_ meaningful. That tainted flag makes it extremely
difficult to do deals with mainstream Linux companies and there is always
the fear that it will turn into a legal problem. The latter bit tends to
make venture capitalists nervous.
That said, the EXPORT_GPL issue is not about black and white legal issues,
it is about gentle encouragement. In this case we are offering a clumsy,
on-the-metal, guaranteed-to-change-and-make-you-edit-code interface to
non-GPL-compatible modules and a decent, stable (in the deserves to live
sense) interface for the pure of heart. Gentle encouragement at exactly
the right level.
Did we settle the question of whether these particular exports should be
EXPORT_SYMBOL_GPL?
Regards,
Daniel
next prev parent reply other threads:[~2006-06-14 17:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 23:56 [RFC/PATCH 1/2] in-kernel sockets API Sridhar Samudrala
2006-06-13 5:07 ` Stephen Hemminger
2006-06-13 11:13 ` Arnaldo Carvalho de Melo
2006-06-13 11:22 ` Brian F. G. Bidulock
2006-06-13 21:12 ` Daniel Phillips
2006-06-13 21:40 ` Brian F. G. Bidulock
2006-06-13 22:00 ` Chase Venters
2006-06-13 22:30 ` Daniel Phillips
2006-06-13 22:47 ` Brian F. G. Bidulock
2006-06-13 23:59 ` Chase Venters
2006-06-14 0:31 ` Brian F. G. Bidulock
2006-06-14 0:53 ` Chase Venters
2006-06-14 6:07 ` Brian F. G. Bidulock
2006-06-14 7:58 ` Chase Venters
2006-06-14 9:28 ` Brian F. G. Bidulock
2006-06-14 10:43 ` Alan Cox
2006-06-14 10:54 ` Brian F. G. Bidulock
2006-06-14 10:36 ` Theodore Tso
2006-06-13 22:44 ` Brian F. G. Bidulock
2006-06-13 23:42 ` Ben Greear
2006-06-14 0:05 ` Chase Venters
2006-06-14 0:18 ` Brian F. G. Bidulock
2006-06-14 0:29 ` Chase Venters
2006-06-14 0:36 ` Brian F. G. Bidulock
2006-06-14 0:19 ` Ben Greear
2006-06-14 0:38 ` Brian F. G. Bidulock
2006-06-14 13:30 ` Harald Welte
2006-06-14 14:29 ` Erik Mouw
2006-06-14 15:26 ` Harald Welte
2006-06-14 17:48 ` Daniel Phillips [this message]
2006-06-14 18:03 ` Brian F. G. Bidulock
2006-06-14 20:52 ` Sridhar Samudrala
2006-06-13 14:58 ` Jan Engelhardt
2006-06-13 16:27 ` Sridhar Samudrala
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=44904C08.6020307@google.com \
--to=phillips@google.com \
--cc=bidulock@openss7.org \
--cc=laforge@gnumonks.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=sri@us.ibm.com \
/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).