From: Paolo Bonzini <pbonzini@redhat.com>
To: Andrew Jones <drjones@redhat.com>, kvm@vger.kernel.org
Cc: alex.bennee@linaro.org, andre.przywara@arm.com, wei@redhat.com,
lkurusa@redhat.com
Subject: Re: [kvm-unit-tests RFC PATCH 0/2] try another approach for uapi headers
Date: Thu, 10 Sep 2015 18:24:28 +0200 [thread overview]
Message-ID: <55F1AEBC.1040604@redhat.com> (raw)
In-Reply-To: <1441884716-15355-1-git-send-email-drjones@redhat.com>
On 10/09/2015 13:31, Andrew Jones wrote:
> Rather than import uapi headers, just include them. I've put an RFC on
> this series because it will now require kernel headers to be installed on
> the build machine. I'm guessing that's not a big problem, but before we
> commit to it, it'd be good to hear opinions from others.
>
> This change wouldn't be worth it just for psci.h, but we're looking at PCI
> support now, and thus we'll also want pci.h (and pci_regs.h). Although
> after pci.h I'm not sure what else we'll eventually want. If nothing, then
> maybe importing pci.h is also the right thing to do?
Sounds good, and it's a tiny bit easier to go include->import than
import->include.
Paolo
prev parent reply other threads:[~2015-09-10 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 11:31 [kvm-unit-tests RFC PATCH 0/2] try another approach for uapi headers Andrew Jones
2015-09-10 11:31 ` [kvm-unit-tests RFC PATCH 1/2] lib: link in linux kernel headers (uapi) Andrew Jones
2015-09-10 11:31 ` [kvm-unit-tests RFC PATCH 2/2] Revert "arm/arm64: import include/uapi/linux/psci.h" Andrew Jones
2015-09-10 16:24 ` Paolo Bonzini [this message]
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=55F1AEBC.1040604@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=andre.przywara@arm.com \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lkurusa@redhat.com \
--cc=wei@redhat.com \
/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).