From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [kvm-unit-tests RFC PATCH 0/2] try another approach for uapi headers Date: Thu, 10 Sep 2015 18:24:28 +0200 Message-ID: <55F1AEBC.1040604@redhat.com> References: <1441884716-15355-1-git-send-email-drjones@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: alex.bennee@linaro.org, andre.przywara@arm.com, wei@redhat.com, lkurusa@redhat.com To: Andrew Jones , kvm@vger.kernel.org Return-path: Received: from mx1.redhat.com ([209.132.183.28]:48081 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751489AbbIJQYe (ORCPT ); Thu, 10 Sep 2015 12:24:34 -0400 In-Reply-To: <1441884716-15355-1-git-send-email-drjones@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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