qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Rusty Russell <rusty@rustcorp.com.au>, kvm <kvm@vger.kernel.org>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Alexander Graf <agraf@suse.de>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] Import Linux headers for KVM and vhost
Date: Wed, 4 May 2011 00:37:46 +0300	[thread overview]
Message-ID: <20110503213746.GA6774@redhat.com> (raw)
In-Reply-To: <4DC0426A.5090008@codemonkey.ws>

On Tue, May 03, 2011 at 12:59:06PM -0500, Anthony Liguori wrote:
> On 05/03/2011 12:55 PM, Jan Kiszka wrote:
> >On 2011-05-03 19:45, Anthony Liguori wrote:
> >>On 05/03/2011 12:30 PM, Peter Maydell wrote:
> >>>On 3 May 2011 17:48, Jan Kiszka<jan.kiszka@siemens.com>   wrote:
> >>>>Kernel headers were automatically imported from current kvm.git,
> >>>>93c016c8c4. Some are not covered by any license and can be considered
> >>>>GPLv2 with user space exception.
> >>>
> >>>Hmm. Can't we just get whoever owns those files to apply a suitable
> >>>copyright and license header to them? Committing files to qemu.git
> >>>which don't have a clear (and clearly stated) copyright/license seems
> >>>like a bad plan to me...
> >>
> >>Which are the headers in question?
> >
> >include/asm-powerpc:	explicit GPLv2
> >include/asm-s390:	explicit GPLv2
> >include/asm/x86:	no license mentioned
> >include/linux/kvm*:	no license mentioned
> >include/linux/vhost:	no license mentioned
> 
> Michael/Avi, can ya'll add copyrights/licenses as appropriate?

All kernel is GPLv2 with userspace exceptions.  The explicit GPLv2
licenses are likely uninitentional.  So I don't really believe licenses
are applicable in headers, we see how this creates confusion.

Just place the kernel COPYING file into the include directory?

> >include/linux/virtio*:	"BSB"
> >
> >The last group already popped up here during a license clearing of the
> >kernel. I contacted Rusty on them and got the answer "Standard 3 clause.
> >  The 4 clause is incompatible with the GPL." That was OK for our
> >purposes, but I nevertheless asked Rusty to push a clarifying sentence
> >to the kernel - unfortunately this did not happen so far.
> 
> Rusty, do you want to put together a patch with the full license or
> should I?
> 
> Regards,
> 
> Anthony Liguori
> 
> >
> >Jan
> >

  reply	other threads:[~2011-05-03 21:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-03 14:05 [Qemu-devel] [RFC][PATCH] Import Linux headers for KVM and vhost Jan Kiszka
2011-05-03 15:12 ` Christoph Hellwig
2011-05-03 15:32   ` Jan Kiszka
2011-05-03 15:41 ` Arnd Bergmann
2011-05-03 16:48 ` [Qemu-devel] [PATCH v2] " Jan Kiszka
2011-05-03 16:55   ` Avi Kivity
2011-05-03 17:09     ` Jan Kiszka
2011-05-03 17:13       ` Avi Kivity
2011-05-03 17:32         ` Edgar E. Iglesias
2011-05-03 17:39           ` Jan Kiszka
2011-05-03 17:57           ` Scott Wood
2011-05-03 19:26             ` Arnd Bergmann
2011-05-03 17:30   ` Peter Maydell
2011-05-03 17:42     ` Jan Kiszka
2011-05-03 17:45     ` Anthony Liguori
2011-05-03 17:55       ` Jan Kiszka
2011-05-03 17:59         ` Anthony Liguori
2011-05-03 21:37           ` Michael S. Tsirkin [this message]
2011-05-04  8:55             ` Jan Kiszka
2011-05-09  3:24               ` Rusty Russell
2011-05-03 20:22   ` Peter Maydell
2011-05-04 10:28     ` Jan Kiszka
2011-05-04 17:58       ` Andreas Färber
2011-05-04 18:01         ` Jan Kiszka

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=20110503213746.GA6774@redhat.com \
    --to=mst@redhat.com \
    --cc=agraf@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rusty@rustcorp.com.au \
    /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).