All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>,
	Nitin Gupta <nitingupta910@gmail.com>
Cc: Diwaker Gupta <dgupta@cs.ucsd.edu>,
	kurt.hackel@oracle.com,
	"Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>
Subject: Re: [RFC] Replacing Xen's xmalloc engine and(?) API
Date: Sun, 12 Oct 2008 19:34:07 +0100	[thread overview]
Message-ID: <C51801AF.1E1B0%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <b1ab7bf7-8a72-49ef-a912-88a5cfbc7557@default>

On 12/10/08 19:03, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:

> Excellent!  Your xvMalloc looks even better!  I'll read the
> code and try it (tomorrow).
> 
> Keir, is a "GNU Lesser GPL Version 3" license OK for Xen?

Unfortunately I doubt it, since Xen is GPLv2 and we wouldn't really be
linking against xvMalloc as a separate library (not least because it would
probably get tailored a bit to get checked into the Xen tree) so the
'Lesser' license probably doesn't apply. If Nitin isn't too attached to
GPLv3 it would certainly be better for us if it used GPLv2, like TLSF.

 -- Keir

  reply	other threads:[~2008-10-12 18:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4cefeab80810121044j44687af3s78574b41c7a9ab04@mail.gmail.com>
2008-10-12 17:55 ` [RFC] Replacing Xen's xmalloc engine and(?) API Keir Fraser
2008-10-12 18:03 ` Dan Magenheimer
2008-10-12 18:34   ` Keir Fraser [this message]
2008-10-11 21:44 Dan Magenheimer
2008-10-11 22:12 ` Stefan de Konink
2008-10-11 22:59   ` Dan Magenheimer
2008-10-12  9:16 ` Keir Fraser
2008-10-12 10:25   ` Keir Fraser
2008-10-12 16:28     ` Dan Magenheimer
2008-10-12 16:47       ` Keir Fraser
2008-10-12 17:31         ` Dan Magenheimer
2008-10-12 17:42           ` Keir Fraser

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=C51801AF.1E1B0%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=dgupta@cs.ucsd.edu \
    --cc=kurt.hackel@oracle.com \
    --cc=nitingupta910@gmail.com \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.