From: Wei Liu <liuw@liuw.name>
To: Eric Blake <eblake@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
xen-devel <xen-devel@lists.xensource.com>,
"Wei Liu (Intern)" <wei.liu2@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
QEMU-devel <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] Xen: Add xen-apic support and hook it up.
Date: Thu, 12 Apr 2012 11:23:17 +0800 [thread overview]
Message-ID: <CAOsiSVVjxpZAW4GOMto9qoEMgGQUgfTD9b1SDT2uqH+Oa8O0SQ@mail.gmail.com> (raw)
In-Reply-To: <4F85B925.6090309@redhat.com>
On Thu, Apr 12, 2012 at 1:02 AM, Eric Blake <eblake@redhat.com> wrote:
> On 04/11/2012 10:17 AM, Stefano Stabellini wrote:
>> On Wed, 11 Apr 2012, Peter Maydell wrote:
>>> On 5 April 2012 10:35, Wei Liu <wei.liu2@citrix.com> wrote:
>>>>
>>>> --- /dev/null
>>>> +++ b/hw/xen_apic.c
>>>> @@ -0,0 +1,90 @@
>>>> +/*
>>>> + * Xen basic APIC support
>>>> + *
>>>> + * Copyright (c) 2012 Citrix
>>>> + *
>>>> + * Authors:
>>>> + * Wei Liu <wei.liu2@citrix.com>
>>>> + *
>>>> + * This work is licensed under the terms of the GNU GPL version 2.
>>>> + * See the COPYING file in the top-level directory.
>>>> + */
>>>
>>> Really 2-only, not 2-or-later ?
>>
>> I am not a great fun of the 2-or-later clause and it doesn't look like a
>> requirement from the QEMU project POV. However if it is, I'll change it
>> to 2-or-later.
>
> Conversely, I am not a great fan of the 2-only clause, as it prevents
> reuse of qemu code in other projects. There's a reason that qemu is now
> favoring 2-or-later for new submissions.
>
> http://wiki.qemu.org/Relicensing
>
I don't mind changing the licensing to 2-or-later for greater benefit.
Stefano, please do whatever you need to.
Wei.
> --
> Eric Blake eblake@redhat.com +1-919-301-3266
> Libvirt virtualization library http://libvirt.org
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-04-12 3:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 9:32 [Qemu-devel] [PATCH 0/0] MSI/MSIX injection for Xen HVM guests Wei Liu
2012-04-05 9:32 ` Wei Liu
2012-04-05 9:34 ` [Qemu-devel] [PATCH 1/2] Xen: basic HVM MSI injection support Wei Liu
2012-04-05 9:34 ` Wei Liu
2012-04-05 9:35 ` [Qemu-devel] [PATCH 2/2] Xen: Add xen-apic support and hook it up Wei Liu
2012-04-05 9:35 ` Wei Liu
2012-04-11 16:02 ` Stefano Stabellini
2012-04-11 16:01 ` Jan Kiszka
2012-04-11 16:07 ` Peter Maydell
2012-04-11 16:13 ` Jan Kiszka
2012-04-11 16:23 ` Peter Maydell
2012-04-11 16:17 ` Stefano Stabellini
2012-04-11 16:19 ` Stefano Stabellini
2012-04-11 17:02 ` Eric Blake
2012-04-12 3:23 ` Wei Liu [this message]
2012-04-11 21:37 ` Paolo Bonzini
2012-04-05 10:14 ` [Qemu-devel] [PATCH 0/0] MSI/MSIX injection for Xen HVM guests Paolo Bonzini
2012-04-05 10:14 ` Paolo Bonzini
2012-04-05 10:43 ` [Qemu-devel] " Stefano Stabellini
2012-04-05 10:43 ` Stefano Stabellini
2012-04-05 10:50 ` [Qemu-devel] " Paolo Bonzini
2012-04-05 10:50 ` Paolo Bonzini
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=CAOsiSVVjxpZAW4GOMto9qoEMgGQUgfTD9b1SDT2uqH+Oa8O0SQ@mail.gmail.com \
--to=liuw@liuw.name \
--cc=eblake@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.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.