From: John Levon <moz@compsoc.man.ac.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: Tainting kernels for non-GPL or forced modules
Date: Mon, 24 Sep 2001 19:10:39 +0100 [thread overview]
Message-ID: <20010924191038.A76887@compsoc.man.ac.uk> (raw)
In-Reply-To: <27975.1001164529@ocs3.intra.ocs.com.au> <3BAF74B8.6070102@interactivesi.com>
In-Reply-To: <3BAF74B8.6070102@interactivesi.com>
On Mon, Sep 24, 2001 at 01:00:24PM -0500, Timur Tabi wrote:
> The reason I ask is because I'm working on a closed-source (unfortunately)
> driver for Linux, and I'd really like to make it behave as well as possible.
add to your module code :
MODULE_LICENSE("TabiPL");
(or whatever it is).
That way the kernel maintainers can ignore any bugs reported with your module
loaded easily.
regards
john
--
"Khendon's Law: If the same point is made twice by the same person,
the thread is over."
next prev parent reply other threads:[~2001-09-24 18:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-22 13:15 Keith Owens
2001-09-22 13:33 ` André Dahlqvist
2001-09-22 16:00 ` Tom Rini
2001-09-22 16:05 ` Alan Cox
2001-09-23 1:56 ` Keith Owens
2001-09-22 20:28 ` Albert D. Cahalan
2001-09-23 1:48 ` Keith Owens
2001-09-24 18:00 ` Timur Tabi
2001-09-24 18:10 ` John Levon [this message]
2001-09-24 22:48 ` Keith Owens
2001-09-24 23:31 ` 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=20010924191038.A76887@compsoc.man.ac.uk \
--to=moz@compsoc.man.ac.uk \
--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
Powered by JetHome