All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Anthony Liguori <aliguori@us.ibm.com>, kvm <kvm@vger.kernel.org>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Alexander Graf <agraf@suse.de>,
	qemu-devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>
Subject: Re: [PATCH v2] Import Linux headers for KVM and vhost
Date: Wed, 04 May 2011 12:28:32 +0200	[thread overview]
Message-ID: <4DC12A50.1000800@siemens.com> (raw)
In-Reply-To: <BANLkTinr-G36+zy=0B1U6D-4-6hnn3GRmg@mail.gmail.com>

On 2011-05-03 22:22, Peter Maydell wrote:
> On 3 May 2011 17:48, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>> +++ b/scripts/update-linux-headers.sh
>> @@ -0,0 +1,47 @@
>> +#!/bin/sh
> 
> No -e ?
> 
>> +rm -rf $output/include/linux/*
> 
> Given that updating the kernel headers will blow away large
> subsets of include/ like this, maybe we should use a less generic
> name than "include", so it's clear that it's just a set of
> automatically maintained and updated files, rather than
> a good place to put random QEMU header files?
> 
> kernel-headers/ seems like an obvious choice.
> 
> Is it worth having a README in the directory saying "don't
> edit these, they are copies of the kernel headers, they can
> be updated with <whatever>", or is that unnecessary?
> 

No, these suggestion all make sense. I've incorporated them.

Thanks,
Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Anthony Liguori <aliguori@us.ibm.com>, kvm <kvm@vger.kernel.org>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Alexander Graf <agraf@suse.de>,
	qemu-devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] Import Linux headers for KVM and vhost
Date: Wed, 04 May 2011 12:28:32 +0200	[thread overview]
Message-ID: <4DC12A50.1000800@siemens.com> (raw)
In-Reply-To: <BANLkTinr-G36+zy=0B1U6D-4-6hnn3GRmg@mail.gmail.com>

On 2011-05-03 22:22, Peter Maydell wrote:
> On 3 May 2011 17:48, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>> +++ b/scripts/update-linux-headers.sh
>> @@ -0,0 +1,47 @@
>> +#!/bin/sh
> 
> No -e ?
> 
>> +rm -rf $output/include/linux/*
> 
> Given that updating the kernel headers will blow away large
> subsets of include/ like this, maybe we should use a less generic
> name than "include", so it's clear that it's just a set of
> automatically maintained and updated files, rather than
> a good place to put random QEMU header files?
> 
> kernel-headers/ seems like an obvious choice.
> 
> Is it worth having a README in the directory saying "don't
> edit these, they are copies of the kernel headers, they can
> be updated with <whatever>", or is that unnecessary?
> 

No, these suggestion all make sense. I've incorporated them.

Thanks,
Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2011-05-04 10:28 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-03 14:05 [RFC][PATCH] Import Linux headers for KVM and vhost Jan Kiszka
2011-05-03 14:05 ` [Qemu-devel] " Jan Kiszka
2011-05-03 15:12 ` Christoph Hellwig
2011-05-03 15:12   ` Christoph Hellwig
2011-05-03 15:32   ` Jan Kiszka
2011-05-03 15:32     ` Jan Kiszka
2011-05-03 15:41 ` Arnd Bergmann
2011-05-03 15:41   ` [Qemu-devel] " Arnd Bergmann
2011-05-03 16:48 ` [PATCH v2] " Jan Kiszka
2011-05-03 16:48   ` [Qemu-devel] " Jan Kiszka
2011-05-03 16:55   ` Avi Kivity
2011-05-03 16:55     ` [Qemu-devel] " Avi Kivity
2011-05-03 17:09     ` Jan Kiszka
2011-05-03 17:09       ` [Qemu-devel] " Jan Kiszka
2011-05-03 17:13       ` Avi Kivity
2011-05-03 17:13         ` [Qemu-devel] " Avi Kivity
2011-05-03 17:32         ` Edgar E. Iglesias
2011-05-03 17:32           ` [Qemu-devel] " Edgar E. Iglesias
2011-05-03 17:39           ` Jan Kiszka
2011-05-03 17:39             ` [Qemu-devel] " Jan Kiszka
2011-05-03 17:57           ` Scott Wood
2011-05-03 17:57             ` Scott Wood
2011-05-03 19:26             ` Arnd Bergmann
2011-05-03 19:26               ` Arnd Bergmann
2011-05-03 17:30   ` Peter Maydell
2011-05-03 17:30     ` Peter Maydell
2011-05-03 17:42     ` Jan Kiszka
2011-05-03 17:42       ` [Qemu-devel] " Jan Kiszka
2011-05-03 17:45     ` Anthony Liguori
2011-05-03 17:45       ` Anthony Liguori
2011-05-03 17:55       ` Jan Kiszka
2011-05-03 17:55         ` [Qemu-devel] " Jan Kiszka
2011-05-03 17:59         ` Anthony Liguori
2011-05-03 17:59           ` Anthony Liguori
2011-05-03 21:37           ` Michael S. Tsirkin
2011-05-03 21:37             ` [Qemu-devel] " Michael S. Tsirkin
2011-05-04  8:55             ` Jan Kiszka
2011-05-04  8:55               ` [Qemu-devel] " Jan Kiszka
2011-05-09  3:24               ` Rusty Russell
2011-05-09  3:24                 ` [Qemu-devel] " Rusty Russell
2011-05-03 20:22   ` Peter Maydell
2011-05-03 20:22     ` Peter Maydell
2011-05-04 10:28     ` Jan Kiszka [this message]
2011-05-04 10:28       ` Jan Kiszka
2011-05-04 17:58       ` Andreas Färber
2011-05-04 18:01         ` Jan Kiszka
2011-05-04 18:01           ` [Qemu-devel] " 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=4DC12A50.1000800@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=agraf@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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 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.