mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bernd Petrovitsch <bernd@firmix.at>
To: Giridhar Pemmasani <pgiri@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: incorrect taint of ndiswrapper
Date: Mon, 23 Oct 2006 10:24:06 +0200	[thread overview]
Message-ID: <1161591846.12449.4.camel@tara.firmix.at> (raw)
In-Reply-To: <20061023054119.75745.qmail@web32415.mail.mud.yahoo.com>

On Sun, 2006-10-22 at 22:41 -0700, Giridhar Pemmasani wrote:
> It seems that the kernel module loader taints ndiswrapper module as
> proprietary, but it is not - it is fully GPL: see
> http://directory.fsf.org/sysadmin/hookup/ndiswrapper.html
> 
> Note that when a driver is loaded, ndiswrapper does taint the kernel (to be
> more accurate, it should check if the driver being loaded is GPL or not, but
> that is not done).

There is no reason (apart from "it hasn't been done yet2 which is a very
weak reason) to use ndiswrapper with a GPL-module - just port the
GPL-module over.

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services


  parent reply	other threads:[~2006-10-23  8:24 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-23  5:41 Giridhar Pemmasani
2006-10-23  5:53 ` Gianluca Alberici
2006-10-23  6:25 ` Chase Venters
2006-10-23  6:41   ` Giridhar Pemmasani
2006-10-23  6:48     ` Gianluca Alberici
2006-10-23  7:12     ` Chase Venters
2006-10-23 11:07       ` Giridhar Pemmasani
2006-10-23  9:10     ` Gianluca Alberici
2006-10-23  9:39     ` Michal Schmidt
2006-10-23  8:24 ` Bernd Petrovitsch [this message]
2006-10-23 10:41 ` Alan Cox
2006-10-23 11:35   ` Giridhar Pemmasani
2006-10-23 13:00     ` Alan Cox
2006-10-24  2:43       ` Giridhar Pemmasani
2006-10-24  3:11         ` Randy Dunlap
2006-10-24 12:12           ` Pekka Enberg
2006-10-24 12:22             ` Alan Cox
2006-10-24 14:07         ` Alan Cox
2006-10-23 18:36   ` Zan Lynx
2006-10-24 11:59     ` Jan Engelhardt
2006-10-25 20:11 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-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=1161591846.12449.4.camel@tara.firmix.at \
    --to=bernd@firmix.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pgiri@yahoo.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

all inboxes | Powered by JetHome®