public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Muli Ben-Yehuda <mulix@actcom.co.il>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org
Subject: change ppp_deflate.o module license string [was: ppp_deflate.o taints the kernel?]
Date: Fri, 24 May 2002 21:49:35 +0300	[thread overview]
Message-ID: <20020524214935.B18922@actcom.co.il> (raw)
In-Reply-To: <E17BGhc-0006V7-00@the-village.bc.nu> <29311.1022254271@redhat.com>

Marcelo, 

Please apply trivial patch to ppp_deflate.o to change module license
to dual BSD/GPL, like 2.5, in order to avoid needlessly tainting the
kernel. 

diff -ur linux-2.4.19-pre8-vanilla/drivers/net/ppp_deflate.c linux-2.4.19-pre8/drivers/net/ppp_deflate.c
--- linux-2.4.19-pre8-vanilla/drivers/net/ppp_deflate.c	Sun Sep 30 21:26:07 2001
+++ linux-2.4.19-pre8/drivers/net/ppp_deflate.c	Fri May 24 21:43:44 2002
@@ -657,4 +657,4 @@
 
 module_init(deflate_init);
 module_exit(deflate_cleanup);
-MODULE_LICENSE("BSD without advertisement clause");
+MODULE_LICENSE("Dual BSD/GPL");

On Fri, May 24, 2002 at 04:31:11PM +0100, David Woodhouse wrote:
> 
> alan@lxorguk.ukuu.org.uk said:
> >  FAQ item - BSD license doesnt guarantee we have source. If its GPL
> > compatible someone should slap a GPL header on our copy and be done
> > with it
> 
> It's already marked 'Dual BSD/GPL' in your tree and in 2.5, I believe.
> I fixed it when I did the zlib changes.
-- 
Trewsday 2 Forelithe 7466

http://vipe.technion.ac.il/~mulix/
http://syscalltrack.sf.net/

      reply	other threads:[~2002-05-24 18:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-23 16:35 ppp_deflate.o taints the kernel? Muli Ben-Yehuda
2002-05-24 15:10 ` Alan Cox
2002-05-24 15:31   ` David Woodhouse
2002-05-24 18:49     ` Muli Ben-Yehuda [this message]

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=20020524214935.B18922@actcom.co.il \
    --to=mulix@actcom.co.il \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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