[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <64526782-26fb-0012-f467-b6e5a1ab6357@redhat.com>
Date: Mon, 2 Jan 2017 09:19:57 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Roman Kagan <rkagan@...tuozzo.com>,
KY Srinivasan <kys@...rosoft.com>,
Stephen Hemminger <stephen@...workplumber.org>,
Christoph Hellwig <hch@...radead.org>,
Radim Krčmář <rkrcmar@...hat.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"Denis V . Lunev" <den@...nvz.org>,
Haiyang Zhang <haiyangz@...rosoft.com>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 12/15] hyperv: move VMBus connection ids to uapi
On 28/12/2016 18:09, Roman Kagan wrote:
> Am I correct assuming that QEMU is currently the only user of
> arch/x86/include/uapi/asm/hyperv.h?
>
> Then I think we're fine withdrawing it from uapi as a whole and letting
> QEMU pull it in through its header-harvesting scripts (as does now
> anyway). This would lift all licensing and longterm API stability
> expectations.
Actually, QEMU's header-harvesting scripts use uapi/ headers
exclusively, since they are built on "make headers_install".
The extra cleanups that QEMU does on top are to allow compilation of the
headers on non-Linux machines. They don't really do much more than
changing Linux (linux/types.h) integer types to the C99 (stdint.h)
equivalents.
Paolo
Powered by blists - more mailing lists