xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Lars Kurth <lars.kurth@citrix.com>,
	Lars Kurth <lars.kurth.xen@gmail.com>,
	Ian Jackson <Ian.Jackson@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: ACPI builder re-licensing
Date: Wed, 13 Jul 2016 14:19:20 -0400	[thread overview]
Message-ID: <36352571-4e36-0c83-ecd3-dc925823a32b@oracle.com> (raw)
In-Reply-To: <D3AC0DF1.2B3E2%lars.kurth@citrix.com>

On 07/13/2016 10:30 AM, Lars Kurth wrote:
>
> On 13/07/2016 15:22, "Boris Ostrovsky" <boris.ostrovsky@oracle.com> wrote:
>
>> On 07/13/2016 09:21 AM, Lars Kurth wrote:
>>> Boris,
>>>
>>> I can't remember how we managed this process the last time round (see
>>> for https://patchwork.kernel.org/patch/9172431/), but in that case we
>>> already had a patch. As far as I can see, we don't have the complete
>>> patch yet.
>>>
>>> Thus, the question I would have to you is whether you want to prepare
>>> the complete patch first or get the approvals of all stake-holders first?
>> I certainly can (and should) prepare and post the patch but I thought we
>> should first come up with (A) list at the least.
> It's basically in this thread already and is
> - Kouya Shimura <kouya@jp.fujitsu.com>
> - Daniel's old private e-mail address, if still active.
> - Stefan Berger <stefanb@us.ibm.com>
> - Simon Horman <horms@verge.net.au>
> - Keir <keir@xen.org>
>  
> Possibly Paolo
>
>> OTOH, we can at least
>> review the patch first here on xen-devel without bothering people from
>> that list with revisions. So yes, I will.


Which LGPL version are we using?

Most libxc and all libxl files say it's strictly 2.1: "... version 2.1
only. with the special exception on linking described in file LICENSE"
(with LICENSE file not provided, which I assume meaning that it's
vanilla 2.1).

However, some files in libxc are less restrictive in this regard:
"either version 2.1 of the License, or (at your option) any later version.".

(I will be out tomorrow and won't respond until Friday)

-boris




_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-07-13 18:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-12 14:55 ACPI builder re-licensing Boris Ostrovsky
2016-07-12 17:09 ` Ian Jackson
2016-07-13 13:21   ` Lars Kurth
2016-07-13 14:22     ` Boris Ostrovsky
2016-07-13 14:30       ` Lars Kurth
2016-07-13 18:19         ` Boris Ostrovsky [this message]
2016-07-14 16:29           ` Lars Kurth
2016-07-14 16:48             ` Ian Jackson
2016-07-14 17:09               ` Lars Kurth

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=36352571-4e36-0c83-ecd3-dc925823a32b@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=Ian.Jackson@citrix.com \
    --cc=lars.kurth.xen@gmail.com \
    --cc=lars.kurth@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).