From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
devel@linuxdriverproject.org, linux-kernel@vger.kernel.org
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
"K . Y . Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [PATCH v1 1/2] hyperv: Include linux/types.h to avoid build break
Date: Sun, 13 Aug 2017 16:39:18 +0300 [thread overview]
Message-ID: <1502631558.15214.2.camel@linux.intel.com> (raw)
In-Reply-To: <20170813133444.23386-1-andriy.shevchenko@linux.intel.com>
On Sun, 2017-08-13 at 16:34 +0300, Andy Shevchenko wrote:
> The commit 2ffd9e33ce4a
>
> ("x86/hyper-v: Use hypercall for remote TLB flush")
>
> introduced a new C-file where uapi/linux/hyperv.h is included first.
>
> This makes build failed since UAPI headers are heavily dependent to
> special
> types of variables, e.g. __u8.
>
> CC arch/x86/hyperv/mmu.o
> In file included from include/linux/hyperv.h:28:0,
> from arch/x86/hyperv/mmu.c:3:
> include/uapi/linux/hyperv.h:71:2: error: unknown type name ‘__u8’
> __u8 operation;
> ^~~~
>
> Include linux/types.h to the UAPI header like many others do.
>
Oops, it's because I have an update to this file in my local uuid
branch.
In any case this is right thing to do independently of uuid.h inclusion.
Please, ignore this patch for now, but note the second one is still
valid.
> Cc: Vitaly Kuznetsov <vkuznets@redhat.com>
> Cc: K. Y. Srinivasan <kys@microsoft.com>
> Cc: Haiyang Zhang <haiyangz@microsoft.com>
> Cc: Stephen Hemminger <sthemmin@microsoft.com>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> include/uapi/linux/hyperv.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/uapi/linux/hyperv.h b/include/uapi/linux/hyperv.h
> index 7560c0aa60e3..aaf32131b556 100644
> --- a/include/uapi/linux/hyperv.h
> +++ b/include/uapi/linux/hyperv.h
> @@ -25,6 +25,8 @@
> #ifndef _UAPI_HYPERV_H
> #define _UAPI_HYPERV_H
>
> +#include <linux/types.h>
> +
> /*
> * Framework version for util services.
> */
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2017-08-13 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-13 13:34 [PATCH v1 1/2] hyperv: Include linux/types.h to avoid build break Andy Shevchenko
2017-08-13 13:34 ` [PATCH v1 2/2] MAINTAINERS: Add missed file for Hyper-V Andy Shevchenko
2017-08-14 10:48 ` [tip:x86/platform] " tip-bot for Andy Shevchenko
2017-08-13 13:39 ` Andy Shevchenko [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=1502631558.15214.2.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=sthemmin@microsoft.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@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