mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	Michal Hocko <mhocko@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Nicolas Dichtel <nicolas.dichtel@6wind.com>,
	Masahiro Yamada <yamada.masahiro@socionext.com>
Subject: Re: microblaze fails to to compile with allmodconfig
Date: Fri, 15 Sep 2017 14:17:48 +0200	[thread overview]
Message-ID: <f52e15fa-65e0-5ccb-3ae3-9d5f5fdfce8d@monstr.eu> (raw)
In-Reply-To: <CAMuHMdVqEYmUR5OQ3rm3LuvCMmrxTnGxMrF4erLFQYoHT+_0HA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1752 bytes --]

Hi Michal and Geert, +Nicolas and Masahiro

On 14.9.2017 11:19, Geert Uytterhoeven wrote:
> Hi Michal,
> 
> On Thu, Sep 14, 2017 at 11:07 AM, Michal Hocko <mhocko@kernel.org> wrote:
>> I've started seeing the following compilation failures with microblaze
>> with the current linux-next (next-20170913). I have no idea when this
>> has been introduced but microblaze clearly doesn't have arch specific
>> kvm_para.h.
>>
>> In file included from ./include/linux/kvm_para.h:4:0,
>>                  from kernel/watchdog.c:29:
>> ./include/uapi/linux/kvm_para.h:32:26: fatal error: asm/kvm_para.h: No such file or directory
>>  #include <asm/kvm_para.h>
>>                           ^
>> compilation terminated.
>> make[1]: *** [kernel/watchdog.o] Error 1
>> make[1]: *** Waiting for unfinished jobs....
>>
>> allyesconfig and allnoconfig compile just fine. Maybe allmodconfig needs
>> an update?


Thanks for reporting this.

> 
> arch/microblaze/include/uapi/asm/Kbuild needs a line
> 
>     generic-y += kvm_para.h
> 
> ?

tile/arm/alpha/frv/nm10300/hexagon/sparc/score have
#include <asm-generic/kvm_para.h>

ppc and x86 contain implementation.

s390 and mips are just empty files

Issue was likely introduced by:
"uapi: export all headers under uapi directories"
(commit fcc8487d477a3452a1d0ccbdd4c5e0e1e3cb8bed)

Where header-y += kvm_para.h was removed.

Masahiro/Nicolas: Any issue with this proposed fix?

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP SoCs



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2017-09-15 12:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-14  9:07 Michal Hocko
2017-09-14  9:19 ` Geert Uytterhoeven
2017-09-15 12:17   ` Michal Simek [this message]
2017-09-15 13:06     ` Masahiro Yamada

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=f52e15fa-65e0-5ccb-3ae3-9d5f5fdfce8d@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=yamada.masahiro@socionext.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

all inboxes | Powered by JetHome®