Subject: Re: [PATCH ??] Re: incorrect taint of ndiswrapper
From: Arjan van de Ven <arjan@infradead.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org, proski@gnu.org,
       Alan Cox <alan@lxorguk.ukuu.org.uk>, cate@debian.org,
       gianluca@abinetworks.biz, Andrew Morton <akpm@osdl.org>
In-Reply-To: <20061026102630.ad191d21.randy.dunlap@oracle.com>
References: <1161807069.3441.33.camel@dv>
	 <1161808227.7615.0.camel@localhost.localdomain>
	 <20061025205923.828c620d.akpm@osdl.org>
	 <20061026102630.ad191d21.randy.dunlap@oracle.com>
Content-Type: text/plain
Organization: Intel International BV
Date: Fri, 27 Oct 2006 16:23:39 +0200
Message-Id: <1161959020.12281.1.camel@laptopd505.fenrus.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1073
Lines: 31


> 
> ---
> From: Randy Dunlap <randy.dunlap@oracle.com>
> 
> For ndiswrapper and driverloader, don't set the module->taints
> flags, just set the kernel global tainted flag.
> This should allow ndiswrapper to continue to use GPL symbols.
> Not tested.


can we put something in feature-removal that we'll undo this in say 6
months?

ndiswrapper is easy to fix to not use the internals of the queue_work
api, and just use schedule_work() instead. At that time the
functionality as a whole is still the right one.
(it's a separate question if ndiswrapper should be in this table;
driverloader should be, it's non-GPL at all, so that part of your patch
is broken)


-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/