From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, ltt-dev@lists.casi.polymtl.ca,
pierre-marc.fournier@polymtl.ca
Subject: Re: Moving Userspace RCU (urcu) from GPL to LGPL license
Date: Wed, 18 Feb 2009 16:44:26 -0500 [thread overview]
Message-ID: <20090218214426.GA30245@Krystal> (raw)
In-Reply-To: <20090218213448.3b467c88@the-village.bc.nu>
* Alan Cox (alan@lxorguk.ukuu.org.uk) wrote:
> On Wed, 18 Feb 2009 13:02:32 -0500
> Mathieu Desnoyers <compudj@krystal.dyndns.org> wrote:
> > only thing is that we cannot put GPL code into a LGPL library.
>
> You'll need a patent grant from IBM for non GPL use for that not just an
> LGPL library
>
> > The other point is that I use a few low-level primitives from the Linux
> > kernel header (e.g. atomic increment for x86, barrier macros). Those are
> > simple one-liners, but, still, I wonder about the licensing
> > implications. I could simply "rewrite" them, but that would be a shame
>
> Ask the author - certainly the original basic atomic ops Linus gave
> specific permission to the mozilla folks to use under other licences.
>
> Alan
>
Thanks Alan for this precious information. I'll discuss with IBM about
possible alternatives.
Mathieu
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
prev parent reply other threads:[~2009-02-18 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 18:02 Moving Userspace RCU (urcu) from GPL to LGPL license Mathieu Desnoyers
2009-02-18 20:06 ` Paul E. McKenney
2009-02-18 20:47 ` Mathieu Desnoyers
2009-02-18 21:34 ` Alan Cox
2009-02-18 21:44 ` Mathieu Desnoyers [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=20090218214426.GA30245@Krystal \
--to=compudj@krystal.dyndns.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@lists.casi.polymtl.ca \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pierre-marc.fournier@polymtl.ca \
/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