From: Anthony Liguori <anthony@codemonkey.ws>
To: Rusty Russell <rusty@rustcorp.com.au>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
virtualization <virtualization@lists.linux-foundation.org>,
qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v2 00/11] qemu: use virtio linux headers in portable code
Date: Wed, 29 May 2013 08:05:29 -0500 [thread overview]
Message-ID: <87hahmq6li.fsf@codemonkey.ws> (raw)
In-Reply-To: <87ip22od5f.fsf@rustcorp.com.au>
Rusty Russell <rusty@rustcorp.com.au> writes:
> Anthony Liguori <anthony@codemonkey.ws> writes:
>> The headers say they are BSD licensed... but they include a GPLv2+
>> header. Doesn't make a lot of sense, does it?
>
> It makes perfect sense: you're overthinking it. It just means that
> copying the BSD headers outside Linux is encouraged.
Copying by hand and modifying. This patch series attempts to do it
automatically within QEMU.
> And it's clearly nonsensical to claim the GPL on kernel headers means
> that userspace needs to be GPL. So please ignore this licensing
> red-herring.
You're missing context, I suspect. This series is trying to
automatically copy the headers from Linux. We currently have a manually
copied version.
The headers are not currently well suited for automatic copying because
(1) they use kernel types (2) they pull in dependencies from throughout
the kernel.
This discussion comes down to whether we want to make it easier to
automatically copy the headers or do we maintain the status quo and
require manual munging to pull in the headers.
Regards,
Anthony Liguori
>
> And we'll bikeshed the headers in the standard when we have to :) They
> certainly don't need to be cut&paste into the kernel sources.
>
> Cheers,
> Rusty.
next prev parent reply other threads:[~2013-05-29 13:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1369581694-1655-1-git-send-email-mst@redhat.com>
[not found] ` <CAFEAcA9stW6xv3mr0ouMVTcDfVE=4=_OcUuZscguJkzGFY9WKg@mail.gmail.com>
[not found] ` <20130526175110.GA3115@redhat.com>
[not found] ` <CAFEAcA9HW6=F7QKpuof02hGTaAnLsZmoZ_-Yo98wKzeELi_zvA@mail.gmail.com>
[not found] ` <20130526181017.GB3115@redhat.com>
[not found] ` <51A253C6.7060303@redhat.com>
[not found] ` <20130526183747.GB3427@redhat.com>
[not found] ` <51A25A2D.8030700@redhat.com>
[not found] ` <20130526200251.GA4305@redhat.com>
[not found] ` <51A26E95.5000207@redhat.com>
2013-05-26 20:49 ` [Qemu-devel] [PATCH v2 00/11] qemu: use virtio linux headers in portable code Anthony Liguori
2013-05-26 21:42 ` Michael S. Tsirkin
2013-05-27 0:55 ` Anthony Liguori
2013-05-27 15:02 ` Michael S. Tsirkin
2013-05-27 16:14 ` Anthony Liguori
2013-05-28 6:23 ` Michael S. Tsirkin
2013-05-29 0:14 ` Rusty Russell
2013-05-29 13:05 ` Anthony Liguori [this message]
2013-05-29 14:09 ` Michael S. Tsirkin
2013-05-29 14:58 ` Anthony Liguori
2013-05-27 11:15 ` Rusty Russell
2013-05-28 2:55 ` Anthony Liguori
2013-05-29 0:17 ` Rusty Russell
2013-05-29 5:17 ` Bryan Venteicher
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=87hahmq6li.fsf@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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).