qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Gleb Natapov <gleb@redhat.com>
Cc: Hollis Blanchard <hollis_blanchard@mentor.com>,
	qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] vhost_net.c broken by --kerneldir
Date: Thu, 26 Aug 2010 17:50:24 +0200	[thread overview]
Message-ID: <201008261750.24256.arnd@arndb.de> (raw)
In-Reply-To: <20100826152142.GV10499@redhat.com>

On Thursday 26 August 2010, Gleb Natapov wrote:
> You forgot about developers. Developer may want to use latest kvm kernel
> headers to compile code that he added to qemu to use new kernel feature.

In that case, you already need to install the kernel in order to test
it, so you might as well install the headers along with it.

Also, you're not normally touching multiple headers at a time, but rather
add a feature in one file, so it's not hard to add it to both copies of
that file. This may seem like an unnecessary step, but using the kernel
headers without installing them first can cause any number of problems
that we don't want anyone to have to deal with.

	Arnd

  parent reply	other threads:[~2010-08-26 16:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-25  0:55 [Qemu-devel] vhost_net.c broken by --kerneldir Hollis Blanchard
2010-08-25 13:37 ` Arnd Bergmann
2010-08-25 17:22   ` Hollis Blanchard
2010-08-26 15:15     ` Arnd Bergmann
2010-08-26 15:21       ` Gleb Natapov
2010-08-26 15:48         ` Anthony Liguori
2010-08-26 16:41           ` Hollis Blanchard
2010-08-26 19:01             ` Anthony Liguori
2010-08-26 15:50         ` Arnd Bergmann [this message]
2010-09-03 10:57       ` Michael S. Tsirkin
2010-08-25 17:21 ` [Qemu-devel] " Hollis Blanchard
2010-08-26  6:29   ` Gleb Natapov

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=201008261750.24256.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=gleb@redhat.com \
    --cc=hollis_blanchard@mentor.com \
    --cc=mst@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).