mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: hps@intermeta.de
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: feature request - why not make netif_rx() a pointer?
Date: 23 Oct 2002 17:11:34 +0100	[thread overview]
Message-ID: <1035389494.3968.63.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <ap6egj$ck$1@forge.intermeta.de>

On Wed, 2002-10-23 at 16:16, Henning P. Schmiedehausen wrote:
> 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.

Thats what lawyers are for. 

> 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.

Not according to lawyers


  reply	other threads:[~2002-10-23 15:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22 21:01 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
2002-10-23 16:11       ` Alan Cox [this message]
2002-10-23 16:26         ` Henning P. Schmiedehausen
2002-10-22 21:30 ` Alan Cox
2002-10-22 22:40 ` David S. Miller
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=1035389494.3968.63.camel@irongate.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=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

all inboxes | Powered by JetHome®