linux-kernel - Re: linux-next: build failure after merge of the qcom 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: <YXYYf9TveqwZRUNp@yoga>
Date:   Sun, 24 Oct 2021 21:37:51 -0500
From:   Bjorn Andersson <bjorn.andersson@...aro.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Andy Gross <agross@...nel.org>,
        Stephan Gerhold <stephan@...hold.net>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the qcom tree

On Sun 24 Oct 18:43 CDT 2021, Stephen Rothwell wrote:

> Hi all,
> 
> After merging the qcom tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/firmware/qcom_scm.c:20:10: fatal error: asm/smp_plat.h: No such file or directory
>    20 | #include <asm/smp_plat.h>
>       |          ^~~~~~~~~~~~~~~~
> 
> Caused by commit
> 
>   55845f46df03 ("firmware: qcom: scm: Add support for MC boot address API")
> 

Thanks for the report Stephen, I will take a look at this.

> I have used the qcom tree from next-20211022 for today.
> 

Thanks,
Bjorn