From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Joerg Roedel <jroedel@suse.de>
Subject: linux-next: build failure after merge of the rpmsg tree
Date: Thu, 26 Apr 2018 13:33:10 +1000 [thread overview]
Message-ID: <20180426133310.0ec74122@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]
Hi Bjorn,
After merging the rpmsg tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
drivers/remoteproc/remoteproc_core.c: In function 'rproc_handle_devmem':
drivers/remoteproc/remoteproc_core.c:557:8: error: implicit declaration of function 'iommu_map_sync'; did you mean 'iommu_map_sg'? [-Werror=implicit-function-declaration]
ret = iommu_map_sync(rproc->domain, rsc->da,
^~~~~~~~~~~~~~
iommu_map_sg
drivers/remoteproc/remoteproc_core.c: In function 'rproc_resource_cleanup':
drivers/remoteproc/remoteproc_core.c:845:14: error: implicit declaration of function 'iommu_unmap_sync'; did you mean 'iommu_unmap_fast'? [-Werror=implicit-function-declaration]
unmapped = iommu_unmap_sync(rproc->domain, entry->da,
^~~~~~~~~~~~~~~~
iommu_unmap_fast
Caused by commit
aace25b18cbd ("remoteproc: Use sychronized interface of the IOMMU-API")
I suspect that part of the commit is missing ...
I have use the rpmsg tree from next-20180424 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-04-26 3:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 3:33 Stephen Rothwell [this message]
2018-04-26 3:46 ` linux-next: build failure after merge of the rpmsg tree Bjorn Andersson
-- strict thread matches above, loose matches on Subject: below --
2023-01-27 7:02 Stephen Rothwell
2023-01-30 8:51 ` Joerg Roedel
2020-10-15 4:55 Stephen Rothwell
2019-02-22 5:18 Stephen Rothwell
2019-02-22 12:50 ` Christoph Hellwig
2019-02-22 14:02 ` Loic PALLARDY
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=20180426133310.0ec74122@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bjorn.andersson@linaro.org \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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).