From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Keith Owens <kaos@ocs.com.au>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Oops on 2.4.13
Date: Fri, 2 Nov 2001 19:41:20 MET-1 [thread overview]
Message-ID: <80D353813B1@vcnet.vc.cvut.cz> (raw)
On 2 Nov 01 at 13:02, Keith Owens wrote:
> drivers/video/matrox/matroxfb_crtc2.o - no license, needs patch
> drivers/video/matrox/matroxfb_g450.o - no license, needs patch
> drivers/video/matrox/matroxfb_maven.o - no license, needs patch
> drivers/video/matrox/matroxfb_misc.o - no license, needs patch
They are all GPL-ed. Does it mean that I have to fix that someone
else changed kernel API during stable serie?
Thanks,
Petr Vandrovec
vandrove@vc.cvut.cz
P.S.: I still do not understand this MODULE_LICENSE() thing. VMware
modules will probably contain GPL tag in next release, but kernel
hackers refuse to look at these reports anyway (I'm not complaining,
this is their right to ignore these reports; but if they say that they
are doing that due to non-GPL, they lie). So I think it should be changed
from MODULE_LICENSE() to
MODULE_CERTIFIED_BY_LINUX_KERNEL_WORKING_GROUP("xxx says it works").
It would match real meaning much better.
next reply other threads:[~2001-11-02 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-02 19:41 Petr Vandrovec [this message]
2001-11-02 18:52 ` Oops on 2.4.13 Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2001-11-01 21:45 FORT David
2001-11-01 22:52 ` Keith Owens
2001-11-02 6:52 ` FORT David
2001-11-02 2:02 ` Keith Owens
2001-11-02 13:00 ` David Chow
2001-11-02 1:39 ` Keith Owens
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=80D353813B1@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=kaos@ocs.com.au \
--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