linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andy Gross <agross@kernel.org>,
	Stephan Gerhold <stephan@gerhold.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the qcom tree
Date: Sun, 24 Oct 2021 21:37:51 -0500	[thread overview]
Message-ID: <YXYYf9TveqwZRUNp@yoga> (raw)
In-Reply-To: <20211025104333.4a3dfb09@canb.auug.org.au>

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

  reply	other threads:[~2021-10-25  2:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-24 23:43 linux-next: build failure after merge of the qcom tree Stephen Rothwell
2021-10-25  2:37 ` Bjorn Andersson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-03 23:30 Stephen Rothwell
2023-12-03 23:23 Stephen Rothwell
2023-09-20 22:42 Stephen Rothwell
2023-09-21  6:30 ` Luca Weiss
2022-11-07 22:00 Stephen Rothwell
2022-11-07 22:15 ` Matti Lehtimäki
2022-11-08  1:30 ` Bjorn Andersson
2020-04-15  0:41 Stephen Rothwell
2020-04-15  1:18 ` John Stultz
2020-04-20 23:29   ` Stephen Rothwell
2020-04-21  2:41     ` John Stultz
2020-05-18  5:16       ` Stephen Rothwell
2020-05-18  6:19         ` Bjorn Andersson
2019-04-23 23:25 Stephen Rothwell
2019-04-23 23:50 ` Matthias Kaehlcke
2018-04-25 22:40 Stephen Rothwell
2018-04-26  3:39 ` Evan Green
2018-04-26  4:52   ` Stephen Rothwell
2018-04-26 16:42     ` Evan Green
2018-04-26 21:23       ` Andy Gross
2016-03-31 23:28 Stephen Rothwell

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=YXYYf9TveqwZRUNp@yoga \
    --to=bjorn.andersson@linaro.org \
    --cc=agross@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=stephan@gerhold.net \
    /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;
as well as URLs for NNTP newsgroup(s).