From: Jan Kiszka Subject: Re: [PATCH v2] Import Linux headers for KVM and vhost Date: Wed, 04 May 2011 20:01:34 +0200 Message-ID: <4DC1947E.2040502@siemens.com> References: <4DC00BB1.7000008@siemens.com> <4DC031CC.1040902@siemens.com> <4DC12A50.1000800@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Peter Maydell , Anthony Liguori , kvm , Marcelo Tosatti , Alexander Graf , qemu-devel , Avi Kivity To: =?ISO-8859-1?Q?Andreas_F=E4rber?= Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org On 2011-05-04 19:58, Andreas F=E4rber wrote: > Am 04.05.2011 um 12:28 schrieb Jan Kiszka: >=20 >> On 2011-05-03 22:22, Peter Maydell wrote: >>> On 3 May 2011 17:48, Jan Kiszka wrote: >>>> +++ b/scripts/update-linux-headers.sh >=20 >>>> +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. >> >> [...] these suggestion all make sense. I've incorporated them. >=20 > If we're talking about a new directory inside the QEMU tree, mind to =20 > name it linux-headers or so? There are other kernels besides The One. := ) Already called it precisely like this. :) I will re-post my series when the licensing things are clarified. Jan --=20 Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux