From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Small PCI core patch
Date: Mon, 21 Nov 2005 15:01:41 -0800 [thread overview]
Message-ID: <20051121230136.GB19212@kroah.com> (raw)
In-Reply-To: <20051121225303.GA19212@kroah.com>
On Mon, Nov 21, 2005 at 02:53:03PM -0800, Greg KH wrote:
> Subject: PCI: fix up the exported symbols to be the proper license.
Ok, now that I have everyone's attention, no I'm not serious about
submitting this patch, I'm not a fool. I know the rules about existing
kernel symbols.
But, what if this patch really did go in? Who would be affected by
this? Nothing that is currently in the kernel.org kernel tree, right,
so what's the big deal?
Oh yeah, closed source drivers that are out side of the tree, but who
cares about them?
Oh yeah, _very_ large companies rely on them right now, and are working
on creating more and more closed source drivers. Why? Don't they know
that their legal departments do not agree with this? Are they
approaching Linux development in the same way they used to with the old
Unix systems, i.e. fork and "add value"?
Well, consider this a warning shot for anyone who is relying on closed
source modules. What you are doing is trying to take from Linux and not
give anything back.. The GPL explicitly forbids this, and Linux would
not be good enough today for you to be using it without that protection.
There is a reason why you are wanting to use Linux for your internal
use, and why your customers are asking for it.
If you, or your company is relying on closed source kernel modules, your
days are numbered. And what are you going to do, and how are you going
to explain things to your bosses and your customers, if possibly,
something like this patch were to be accepted?
Something to think about...
thanks,
greg k-h
next prev parent reply other threads:[~2005-11-21 23:04 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 22:53 [RFC] Small PCI core patch Greg KH
2005-11-21 23:01 ` Greg KH [this message]
2005-11-21 23:35 ` Benjamin Herrenschmidt
2005-11-22 0:47 ` Dave Airlie
2005-11-22 1:34 ` Alan Cox
2005-11-22 2:20 ` Jon Smirl
2005-11-22 2:36 ` Benjamin Herrenschmidt
2005-11-22 3:01 ` Jon Smirl
2005-11-22 7:41 ` Rob Landley
2005-11-22 8:44 ` Dave Airlie
2005-11-22 2:27 ` Benjamin Herrenschmidt
2005-11-22 3:23 ` Jon Smirl
2005-11-22 3:44 ` Benjamin Herrenschmidt
2005-11-22 4:11 ` Neil Brown
2005-11-22 8:07 ` Denis Vlasenko
2005-11-22 14:30 ` Jeff Garzik
2005-11-22 16:33 ` Rob Landley
2005-11-22 16:38 ` Jeff Garzik
2005-11-22 10:58 ` Florian Weimer
2005-11-22 19:28 ` Adrian Bunk
2005-11-23 15:46 ` Jesper Juhl
2005-11-24 2:11 ` Lee Revell
2005-11-22 15:46 ` Avi Kivity
2005-11-22 15:51 ` Jeff Garzik
2005-11-22 16:14 ` Avi Kivity
2005-11-22 16:25 ` Jeff Garzik
2005-11-22 16:40 ` Avi Kivity
2005-11-22 16:56 ` Jeff Garzik
2005-11-22 17:11 ` Avi Kivity
2005-11-22 17:37 ` Brian Gerst
2005-11-22 17:38 ` Jeff Garzik
2005-11-22 19:39 ` Avi Kivity
2005-11-23 10:51 ` Rogério Brito
2005-11-23 14:29 ` Alan Cox
2005-11-22 18:38 ` Alan Cox
2005-11-22 19:47 ` Avi Kivity
2005-11-22 16:26 ` Diego Calleja
2005-11-22 16:35 ` Avi Kivity
2005-11-22 19:49 ` Diego Calleja
2005-11-22 20:08 ` Avi Kivity
2005-11-22 20:15 ` Lee Revell
2005-11-22 20:43 ` Diego Calleja
2005-11-22 22:00 ` Avi Kivity
2005-11-22 22:42 ` Jan Knutar
2005-11-22 14:07 ` Marc Koschewski
2005-11-22 22:53 ` Benjamin Herrenschmidt
2005-11-22 23:06 ` Marc Koschewski
2005-11-22 23:20 ` Benjamin Herrenschmidt
2005-11-22 14:25 ` Alan Cox
2005-11-22 14:26 ` today's graphics (was Re: [RFC] Small PCI core patch) Jeff Garzik
2005-11-22 18:58 ` Alan Cox
2005-11-22 18:41 ` Jeff Garzik
2005-11-22 1:21 ` [RFC] Small PCI core patch Greg KH
2005-11-22 1:28 ` Chris Wedgwood
2005-11-22 1:42 ` Greg KH
2005-11-22 5:50 ` Arjan van de Ven
2005-11-22 14:36 ` Jeff Garzik
2005-11-22 16:54 ` Jon Smirl
2005-11-22 20:17 ` Alan Cox
2005-11-22 21:13 ` Brian Gerst
2005-11-22 23:26 ` Alan Cox
2005-11-22 22:59 ` Benjamin Herrenschmidt
2005-11-22 6:57 ` Rob Landley
2005-11-22 18:26 ` Matthieu CASTET
2005-11-22 19:05 ` Greg KH
2005-11-22 20:15 ` Alan Cox
2005-11-23 3:26 ` Andrew James Wade
2005-11-21 23:28 ` Jeff Garzik
2005-11-21 23:30 ` Benjamin Herrenschmidt
2005-11-22 17:50 ` Greg KH
2005-11-22 22:31 ` Harald Dunkel
2005-11-22 23:40 ` Alan Cox
2005-11-23 6:06 ` Harald Dunkel
2005-11-23 6:26 ` Dave Jones
2005-11-23 11:11 ` Alan Cox
[not found] <5bsXq-5uy-3@gated-at.bofh.it>
[not found] ` <5bsXq-5uy-1@gated-at.bofh.it>
[not found] ` <5btqF-66n-41@gated-at.bofh.it>
[not found] ` <5bzmg-66b-1@gated-at.bofh.it>
[not found] ` <5bHtG-228-23@gated-at.bofh.it>
2005-11-25 4:06 ` Robert Hancock
2005-11-25 6:34 ` Jeff Garzik
2005-11-25 13:54 ` Alan Cox
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=20051121230136.GB19212@kroah.com \
--to=greg@kroah.com \
--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