public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: David Chow <davidchow@shaolinmicro.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: dequeue_signal() in signal.c disabilities
Date: Wed, 24 Nov 2004 23:07:47 +0000	[thread overview]
Message-ID: <1101337666.2571.4.camel@localhost.localdomain> (raw)
In-Reply-To: <41A14E0B.3030608@shaolinmicro.com>

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.


      reply	other threads:[~2004-11-27  0:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-22  2:25 dequeue_signal() in signal.c disabilities David Chow
2004-11-24 23:07 ` Alan Cox [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=1101337666.2571.4.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=davidchow@shaolinmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    /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