From: "David S. Miller" <davem@redhat.com>
To: Slavcho Nikolov <snikolov@okena.com>
Cc: "David S. Miller" <davem@rth.ninka.net>,
jt@hpl.hp.com, Jeff Garzik <jgarzik@mandrakesoft.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: feature request - why not make netif_rx() a pointer?
Date: 24 Oct 2002 06:46:55 -0700 [thread overview]
Message-ID: <1035467215.14435.2.camel@rth.ninka.net> (raw)
In-Reply-To: <000c01c27b61$86c903c0$800a140a@SLNW2K>
On Thu, 2002-10-24 at 06:30, Slavcho Nikolov wrote:
> In other words, the new routine will not be a derivative of the old one
> or some other part of the kernel.
> Instead, I'll create my own (cleanroom) handler that doesn't reuse any
> existing code, which in the end will either pass control to the GPL routine
> being replaced or destroy the parameters and return.
> I can't see how that is a violation of GPL. If it is, then hundreds of
> Linux startups had better go bankrupt now instead of fighting losing
> legal battles later.
Let me give you an example of what would be illegal.
Using this netif_rx() hook to implement a proprietary TCP stack
to replace the GPL'd one in the kernel right now. And that is exactly
the reason I want any such netif_rx function pointer crap to be
EXPORT_GPL
And before someone, I forget who it was, barks again, EXPORT_GPL has
no legal significance, it is merely an annotation. Whether a symbol
is marked this way or not has no consequence on legal matters.
next prev parent reply other threads:[~2002-10-24 13:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
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:23 ` over&out (Re: feature request - why not make netif_rx() a pointer?) Slavcho Nikolov
2002-10-23 22:59 ` jw schultz
2002-10-24 6:25 ` Gilad Ben-Yossef
2002-10-24 7:08 ` Ben Greear
2002-10-25 11:50 ` Adrian Bunk
2002-10-23 16:48 ` feature request - why not make netif_rx() a pointer? 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2002-10-23 16:26 ` Henning P. Schmiedehausen
2002-10-22 21:30 ` Alan Cox
2002-10-22 22:40 ` 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=1035467215.14435.2.camel@rth.ninka.net \
--to=davem@redhat.com \
--cc=davem@rth.ninka.net \
--cc=jgarzik@mandrakesoft.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=snikolov@okena.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
all inboxes | Powered by JetHome®