Subject: Re: dequeue_signal() in signal.c disabilities
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: David Chow <davidchow@shaolinmicro.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
In-Reply-To: <41A14E0B.3030608@shaolinmicro.com>
References: <41A14E0B.3030608@shaolinmicro.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1101337666.2571.4.camel@localhost.localdomain>
Mime-Version: 1.0
Date: Wed, 24 Nov 2004 23:07:47 +0000
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 833
Lines: 18

On Llu, 2004-11-22 at 02:25, David Chow wrote:
> This causes disabilities with modules that are non pure GPL licensed,
> this causes kernel threads or possibly other interrupts unable to be
> handled properly. I've tried both BSD and LGPL which doesn't work. The
> dequeue_signal() is essential to anyone who use sleeps with signals and

If the code is BSD or LGPL licensed then you can stick a GPL license on
the
copy for your kernel anyway and follow the rules for the GPL. That
doesn't in
any way take away the right for it to be used with some other license
separately to the kernel.

-
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/