linux-kernel - Re: linux-next: build failure after merge of the at91 tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20190423072254.qa772iolhha7xb6l@M43218.corp.atmel.com>
Date:   Tue, 23 Apr 2019 09:22:54 +0200
From:   Ludovic Desroches <ludovic.desroches@...rochip.com>
To:     Masahiro Yamada <yamada.masahiro@...ionext.com>
CC:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Nicolas Ferre <nicolas.ferre@...el.com>,
        Alexandre Belloni <alexandre.belloni@...tlin.com>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the at91 tree

On Tue, Apr 23, 2019 at 01:27:52PM +0900, Masahiro Yamada wrote:
> External E-Mail
> 
> 
> On Tue, Apr 23, 2019 at 10:33 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > Hi all,
> >
> > After merging the at91 tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> >
> > arch/arm/mach-at91/pm_suspend.S:17:10: fatal error: pm_data-offsets.h: No such file or directory
> >  #include "pm_data-offsets.h"
> >           ^~~~~~~~~~~~~~~~~~~
> >
> > Caused by commit
> >
> >   ab690fa1eb4b ("ARM: at91: move platform-specific asm-offset.h to arch/arm/mach-at91")
> >
> > I used the version of the at91 tree from next-20190418 for today.
> 
> 
> Sorry, I missed to test the out-of-tree build.
> 
> -I $(srctree)/$(src) is not added
> when check-in assembly files include a generated header.
> (I think this should be automatically cared by Kbuild, though.)
> 
> 
> Ludovic,
> 
> Could you drop this patch for now?

Yes I dropped it from my PR for 5.2 and remove it from at91-next.

Regards

Ludovic