public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Florin Malita <fmalita@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Arjan van de Ven <arjan@infradead.org>,
	linux-kernel@vger.kernel.org, proski@gnu.org, cate@debian.org,
	gianluca@abinetworks.biz
Subject: Re: [PATCH ??] Re: incorrect taint of ndiswrapper
Date: Sat, 28 Oct 2006 00:05:06 +0100	[thread overview]
Message-ID: <1161990307.16839.50.camel@localhost.localdomain> (raw)
In-Reply-To: <45428EAD.6040005@gmail.com>

Ar Gwe, 2006-10-27 am 18:56 -0400, ysgrifennodd Florin Malita:
> Also, since driverloader is not GPL-compatible (MODULE_LICENSE("see
> LICENSE file; Copyright (c)2003-2004 Linuxant inc.")), that check is
> redundant. How about removing it (applies on top of Randy's patch)?
> 
> 
> Signed-off-by: Florin Malita <fmalita@gmail.com>

NAK

Older versions of Linuxant's driverloader claim GPL\0some other text and
systematically set out to abuse the license tag code. We should continue
to carry the code for this.

Alan


  parent reply	other threads:[~2006-10-27 23:02 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-25 20:11 incorrect taint of ndiswrapper Pavel Roskin
2006-10-25 20:30 ` Alan Cox
2006-10-25 20:40   ` Kyle Moffett
2006-10-25 21:04     ` Alan Cox
2006-10-25 21:06   ` Pavel Roskin
2006-10-25 21:33     ` David Weinehall
2006-10-25 22:02       ` Pavel Roskin
2006-10-25 22:54         ` Alan Cox
2006-10-25 22:58       ` Alan Cox
2006-10-26  3:23         ` David Weinehall
2006-10-26 13:13           ` Thierry Vignaud
2006-10-26 13:21             ` Gianluca Alberici
2006-10-26  3:59   ` Andrew Morton
2006-10-26  9:03     ` Gianluca Alberici
2006-10-26 10:39     ` Alan Cox
2006-10-26 12:21       ` Giacomo A. Catenazzi
2006-10-26 12:59         ` Gianluca Alberici
2006-10-26 14:41       ` Al Viro
2006-10-26 14:55         ` Alan Cox
2006-10-26 16:00       ` Stephen Hemminger
2006-10-26 16:26         ` Gianluca Alberici
2006-10-27 14:24           ` Arjan van de Ven
2006-10-27 15:14             ` Stephen Hemminger
2006-10-26 19:19       ` Pavel Roskin
2006-10-26 21:46         ` Adrian Bunk
2006-10-26 22:29           ` Pavel Roskin
2006-10-26 23:00             ` Adrian Bunk
2006-10-26 23:36               ` Sven-Haegar Koch
2006-10-27  0:57                 ` Adrian Bunk
2006-10-26 23:47               ` Pavel Roskin
2006-10-27 12:52             ` Roland Kuhn
2006-10-27 15:53               ` Pavel Roskin
2006-10-26 17:26     ` [PATCH ??] " Randy Dunlap
2006-10-27 14:23       ` Arjan van de Ven
2006-10-27 15:27         ` Randy Dunlap
2006-10-27 18:26           ` Andrew Morton
2006-10-27 22:56             ` Florin Malita
2006-10-27 22:56               ` Randy Dunlap
2006-10-27 23:05               ` Alan Cox [this message]
2006-10-27 23:02                 ` Randy Dunlap
2006-10-27 23:12                 ` Florin Malita
2006-10-27 23:23                 ` Oleg Verych
2006-10-29 11:27             ` Gianluca Alberici
2006-10-27 21:32         ` Florin Malita
2006-10-27  4:32     ` Florin Malita

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=1161990307.16839.50.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=cate@debian.org \
    --cc=fmalita@gmail.com \
    --cc=gianluca@abinetworks.biz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=proski@gnu.org \
    --cc=randy.dunlap@oracle.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