From: "Henning P. Schmiedehausen" <hps@intermeta.de>
To: linux-kernel@vger.kernel.org
Subject: Re: feature request - why not make netif_rx() a pointer?
Date: Wed, 23 Oct 2002 15:16:35 +0000 (UTC) [thread overview]
Message-ID: <ap6egj$ck$1@forge.intermeta.de> (raw)
In-Reply-To: 1035326559.16085.18.camel@rth.ninka.net
"David S. Miller" <davem@rth.ninka.net> writes:
>On Tue, 2002-10-22 at 14:15, Matti Aarnio wrote:
>> ftp://zmailer.org/linux/netif_rx.patch
>Please EXPORT_GPL this, if you are going to do it at all.
>Only non-GPL compliant binary-modules can result from this
>change.
>People can easily do things like implement their own entire
>networking stack with this hook, which is not what we want nor
>is it allowed.
You will never understand, that <insert evil vendor here> can simply
add this modification to the kernel source ("vendor tree"), give this
source away under GPL license and then ship its binary kernel modules
with the source tree.
You won't be able to stop anyone doing this "illegal" thing. But you
hinder many legal users of this.
Not putting an export into the source or exporting GPL_ONLY symbols
won't hinder anyone. Because putting the hooks into a GPL source and
then releasing the result (code + hooks) under GPL is perfectly legal.
The only result are questions on this list, why the <insert your video
card / network / hw driver here> module works under "foobar" Linux and
not with the pristine sources.
Ah and lots of patches like "please put this into the kernel so I can
use the <insert your video card / network / hw driver here> module.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
next prev parent reply other threads:[~2002-10-23 15:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 21:01 feature request - why not make netif_rx() a pointer? Slavcho Nikolov
2002-10-22 21:15 ` Matti Aarnio
2002-10-22 22:42 ` David S. Miller
2002-10-22 23:16 ` Ben Greear
2002-10-22 23:29 ` Jeff Garzik
2002-10-23 15:16 ` Henning P. Schmiedehausen [this message]
2002-10-23 16:11 ` Alan Cox
2002-10-23 16:26 ` Henning P. Schmiedehausen
2002-10-22 21:30 ` Alan Cox
2002-10-22 22:40 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2002-10-23 0:39 Jean Tourrilhes
2002-10-23 13:39 ` Slavcho Nikolov
2002-10-23 14:03 ` Chris Friesen
2002-10-23 16:48 ` Jean Tourrilhes
2002-10-23 17:27 ` Ben Greear
2002-10-24 4:13 ` David S. Miller
2002-10-24 9:28 ` Henning P. Schmiedehausen
2002-10-24 10:15 ` David S. Miller
2002-10-24 11:01 ` Henning Schmiedehausen
2002-10-24 13:30 ` Slavcho Nikolov
2002-10-24 13:46 ` David S. Miller
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='ap6egj$ck$1@forge.intermeta.de' \
--to=hps@intermeta.de \
--cc=linux-kernel@vger.kernel.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).