From: Kouya Shimura <kouya@jp.fujitsu.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Lars Kurth <lars.kurth@citrix.com>, Keir Fraser <keir@xen.org>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Simon Horman <horms@verge.net.au>,
xen-devel@lists.xenproject.org,
Stefan Berger <stefanb@us.ibm.com>,
Daniel Kiper <dkiper@net-space.pl>
Subject: Re: [PATCH] acpi: Re-license ACPI builder files from GPLv2 to LGPLv2.1
Date: Wed, 20 Jul 2016 09:55:49 +0900 [thread overview]
Message-ID: <87vb0186wa.fsf@jp.fujitsu.com> (raw)
In-Reply-To: <OF669C1583.ACD8E63D-ON00257FF5.006B72F4-85257FF5.006B84E9@notes.na.collabserv.com> (Stefan Berger's message of "Tue, 19 Jul 2016 15:34:13 -0400")
Stefan Berger <stefanb@us.ibm.com> writes:
> Daniel Kiper <dkiper@net-space.pl> wrote on 07/19/2016 11:00:04 AM:
>
>> Subject: Re: [PATCH] acpi: Re-license ACPI builder files from GPLv2
>> to LGPLv2.1
>>
>> On Mon, Jul 18, 2016 at 10:01:27AM -0400, Boris Ostrovsky wrote:
>> > ACPI builder is currently distributed under GPLv2 license.
>> >
>> > We plan to make the builder available to components other
>> > than the hvmloader (which is also GPLv2). Some of these
>> > components (such as libxl) may be distributed under LGPL-2.1
>> > so that they can be used by non-GPLv2 callers. But this
>> > will not be possible if we incorporate the ACPI builder in
>> > those other components.
>> >
>> > To avoid this problem we are relicensing sources in ACPI
>> > bulder directory to the Lesser GNU Public License (LGPL)
>> > version 2.1
>> >
>> > Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>> > CC: Kouya Shimura <kouya@jp.fujitsu.com>
>> > CC: Daniel Kiper <dkiper@net-space.pl>
>> > CC: Stefan Berger <stefanb@us.ibm.com>
>> > CC: Simon Horman <horms@verge.net.au>
>> > CC: Keir Fraser <keir@xen.org>
>> > CC: Ian Jackson <ian.jackson@eu.citrix.com>
>> > CC: Lars Kurth <lars.kurth@citrix.com>
>>
>> Acked-by: Daniel Kiper <dkiper@net-space.pl>
> Acked-by: Stefan Berger <stefanb@us.ibm.com>
Acked-by: Kouya Shimura <kouya@jp.fujitsu.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-20 0:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 14:01 [PATCH] acpi: Re-license ACPI builder files from GPLv2 to LGPLv2.1 Boris Ostrovsky
2016-07-19 15:00 ` Daniel Kiper
2016-07-19 19:34 ` Stefan Berger
2016-07-20 0:55 ` Kouya Shimura [this message]
2016-08-01 13:56 ` Boris Ostrovsky
2016-08-01 14:16 ` Jan Beulich
2016-08-04 6:52 ` Tian, Kevin
2016-08-26 13:26 ` Lars Kurth
2016-09-03 0:17 ` Konrad Rzeszutek Wilk
2016-08-15 12:57 ` Boris Ostrovsky
2016-08-26 6:26 ` Simon Horman
2016-08-26 6:54 ` Jan Beulich
2016-08-26 12:13 ` Boris Ostrovsky
2016-08-26 12:51 ` Jan Beulich
2016-08-26 13:08 ` Boris Ostrovsky
2016-08-26 13:29 ` Jan Beulich
2016-08-26 13:23 ` Lars Kurth
[not found] <20160805154726.GA15222@carpenters.cam.cohodata.com>
2016-08-05 17:36 ` 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=87vb0186wa.fsf@jp.fujitsu.com \
--to=kouya@jp.fujitsu.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dkiper@net-space.pl \
--cc=horms@verge.net.au \
--cc=ian.jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=lars.kurth@citrix.com \
--cc=stefanb@us.ibm.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).