From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Bjorn Andersson <bjorn.andersson@linaro•org>
Cc: Pi-Hsun Shih <pihsun@chromium•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the rpmsg tree
Date: Thu, 15 Oct 2020 15:55:49 +1100 [thread overview]
Message-ID: <20201015155549.58724351@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
Hi all,
After merging the rpmsg tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/remoteproc/mtk_scp.c: In function 'mt8192_scp_before_load':
drivers/remoteproc/mtk_scp.c:326:2: error: implicit declaration of function 'dsb' [-Werror=implicit-function-declaration]
326 | dsb(sy);
| ^~~
drivers/remoteproc/mtk_scp.c:326:6: error: 'sy' undeclared (first use in this function); did you mean 's8'?
326 | dsb(sy);
| ^~
| s8
Caused by commit
fd0b6c1ff85a ("remoteproc/mediatek: Add support for mt8192 SCP")
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-10-15 4:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 4:55 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-26 18:44 linux-next: build failure after merge of the rpmsg tree Mark Brown
2024-07-01 7:26 ` Stephen Rothwell
2024-07-01 10:08 ` Dmitry Baryshkov
2023-01-27 7:02 Stephen Rothwell
2023-01-30 8:51 ` Joerg Roedel
2019-02-22 5:18 Stephen Rothwell
2019-02-22 12:50 ` Christoph Hellwig
2019-02-22 14:02 ` Loic PALLARDY
2018-04-26 3:33 Stephen Rothwell
2018-04-26 3:46 ` Bjorn Andersson
2017-08-31 6:54 Stephen Rothwell
2017-08-31 17:47 ` Bjorn Andersson
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=20201015155549.58724351@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=bjorn.andersson@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=pihsun@chromium$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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