From: Joerg Roedel <jroedel@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Joerg Roedel <joro@8bytes.org>, Jason Gunthorpe <jgg@nvidia.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
Srinivasa Rao Mandadapu <quic_srivasam@quicinc.com>,
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 rpmsg tree
Date: Mon, 30 Jan 2023 09:51:51 +0100 [thread overview]
Message-ID: <Y9eFJxQn3y3ig3qw@suse.de> (raw)
In-Reply-To: <20230127180226.783baf07@canb.auug.org.au>
Thanks for the report, Stephen.
Bjorn, Mathieu,
On Fri, Jan 27, 2023 at 06:02:26PM +1100, Stephen Rothwell wrote:
> After merging the rpmsg tree, today's linux-next build (arm64 defconfig)
> failed like this:
>
> drivers/remoteproc/qcom_q6v5_adsp.c: In function 'adsp_map_carveout':
> drivers/remoteproc/qcom_q6v5_adsp.c:369:15: error: too few arguments to function 'iommu_map'
> 369 | ret = iommu_map(rproc->domain, iova, adsp->mem_phys,
> | ^~~~~~~~~
> In file included from drivers/remoteproc/qcom_q6v5_adsp.c:12:
> include/linux/iommu.h:473:12: note: declared here
> 473 | extern int iommu_map(struct iommu_domain *domain, unsigned long iova,
> | ^~~~~~~~~
>
> Caused by commit
>
> f22eedff28af ("remoteproc: qcom: Add support for memory sandbox")
>
> interacting with commit
>
> 1369459b2e21 ("iommu: Add a gfp parameter to iommu_map()")
>
> from the iommu tree.
The patch-set causing this is in a separate branch in the IOMMU tree
which you can be merged into the rpmsg tree for a fixup there:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git iommu-memory-accounting
Regards,
--
Jörg Rödel
jroedel@suse.de
SUSE Software Solutions Germany GmbH
Frankenstraße 146
90461 Nürnberg
Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
next prev parent reply other threads:[~2023-01-30 8:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 7:02 linux-next: build failure after merge of the rpmsg tree Stephen Rothwell
2023-01-30 8:51 ` Joerg Roedel [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-26 18:44 Mark Brown
2024-07-01 7:26 ` Stephen Rothwell
2024-07-01 10:08 ` Dmitry Baryshkov
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
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=Y9eFJxQn3y3ig3qw@suse.de \
--to=jroedel@suse.de \
--cc=bjorn.andersson@linaro.org \
--cc=jgg@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=quic_srivasam@quicinc.com \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.