qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>,
	Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH v2] Import Linux headers for KVM and vhost
Date: Tue, 03 May 2011 19:55:07 +0300	[thread overview]
Message-ID: <4DC0336B.7020106@redhat.com> (raw)
In-Reply-To: <4DC031CC.1040902@siemens.com>

On 05/03/2011 07:48 PM, Jan Kiszka wrote:
> This helps reducing our build-time checks for feature support in the
> available Linux kernel headers. And it helps users that do not have
> sufficiently recent headers installed on their build machine.
>
> Header upstate is triggered via
>
>      scripts/update-linux-headers.sh LINUX_PATH
>
> from the top-level QEMU source directory.
>
> Consequently, the patch removes and build-time checks for kvm and vhost
> in configure, and also the --kerneldir switch. Kernel headers are
> supposed to be provided by QEMU only.
>
> 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. Some are explicitly GPLv2 - at least
> for QEMU that's fine in any case. Others are "BSD" which shall to be
> considered a compatible variant according to Rusty.

Reluctant ack.

(though for commit log cleanliness, the scripts and the headers should 
be in separate commits)

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2011-05-03 16:55 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 [this message]
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
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=4DC0336B.7020106@redhat.com \
    --to=avi@redhat.com \
    --cc=agraf@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=qemu-devel@nongnu.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).