LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Dmitry V. Levin" <ldv@altlinux.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uapi: fix asm/bootparam.h userspace compilation errors
Date: Thu, 5 Apr 2018 09:25:26 +0200	[thread overview]
Message-ID: <32e449e9-5738-d347-20ad-50ee4a2257e2@siemens.com> (raw)
In-Reply-To: <20180405043210.GA13254@altlinux.org>

On 2018-04-05 06:32, Dmitry V. Levin wrote:
> Consistently use types provided by <linux/types.h> to fix the following
> asm/bootparam.h userspace compilation errors:
> 
> /usr/include/asm/bootparam.h:140:2: error: unknown type name 'u16'
>   u16 version;
> /usr/include/asm/bootparam.h:141:2: error: unknown type name 'u16'
>   u16 compatible_version;
> /usr/include/asm/bootparam.h:142:2: error: unknown type name 'u16'
>   u16 pm_timer_address;
> /usr/include/asm/bootparam.h:143:2: error: unknown type name 'u16'
>   u16 num_cpus;
> /usr/include/asm/bootparam.h:144:2: error: unknown type name 'u64'
>   u64 pci_mmconfig_base;
> /usr/include/asm/bootparam.h:145:2: error: unknown type name 'u32'
>   u32 tsc_khz;
> /usr/include/asm/bootparam.h:146:2: error: unknown type name 'u32'
>   u32 apic_khz;
> /usr/include/asm/bootparam.h:147:2: error: unknown type name 'u8'
>   u8 standard_ioapic;
> /usr/include/asm/bootparam.h:148:2: error: unknown type name 'u8'
>   u8 cpu_ids[255];
> 
> Fixes: 4a362601baa6 ("x86/jailhouse: Add infrastructure for running in non-root cell")
> Cc: <stable@vger.kernel.org> # v4.16
> Signed-off-by: Dmitry V. Levin <ldv@altlinux.org>
> ---
>  arch/x86/include/uapi/asm/bootparam.h | 18 +++++++++---------
>  1 file changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/arch/x86/include/uapi/asm/bootparam.h b/arch/x86/include/uapi/asm/bootparam.h
> index aebf60357758..a06cbf019744 100644
> --- a/arch/x86/include/uapi/asm/bootparam.h
> +++ b/arch/x86/include/uapi/asm/bootparam.h
> @@ -137,15 +137,15 @@ struct boot_e820_entry {
>   * setup data structure.
>   */
>  struct jailhouse_setup_data {
> -	u16	version;
> -	u16	compatible_version;
> -	u16	pm_timer_address;
> -	u16	num_cpus;
> -	u64	pci_mmconfig_base;
> -	u32	tsc_khz;
> -	u32	apic_khz;
> -	u8	standard_ioapic;
> -	u8	cpu_ids[255];
> +	__u16	version;
> +	__u16	compatible_version;
> +	__u16	pm_timer_address;
> +	__u16	num_cpus;
> +	__u64	pci_mmconfig_base;
> +	__u32	tsc_khz;
> +	__u32	apic_khz;
> +	__u8	standard_ioapic;
> +	__u8	cpu_ids[255];
>  } __attribute__((packed));
>  
>  /* The so-called "zeropage" */
> 

Acked-by: Jan Kiszka <jan.kiszka@siemens.com>

But how did you trigger this?

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2018-04-05  7:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05  4:32 Dmitry V. Levin
2018-04-05  7:25 ` Jan Kiszka [this message]
2018-04-05 12:20   ` Dmitry V. Levin
2018-04-05  9:18 ` [tip:x86/pti] x86/uapi: Fix " tip-bot for Dmitry V. Levin

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=32e449e9-5738-d347-20ad-50ee4a2257e2@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=ldv@altlinux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --subject='Re: [PATCH] uapi: fix asm/bootparam.h userspace compilation errors' \
    /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

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).