From: Joerg Roedel <joro@8bytes.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Poonam Aggrwal <poonam.aggrwal@nxp.com>,
robh@kernel.org, Joerg Roedel <jroedel@suse.de>,
Arnd Bergmann <arnd@arndb.de>,
Richard Weinberger <richard@nod.at>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
"open list:IOMMU DRIVERS" <iommu@lists.linux-foundation.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
linux-mtd@lists.infradead.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
Suram Suram <suram@nxp.com>,
masonccyang@mxic.com.tw, Will Deacon <will@kernel.org>,
Zhiqiang.Hou@nxp.com
Subject: Re: arm-smmu 5000000.iommu: Cannot accommodate DMA offset for IOMMU page tables
Date: Thu, 24 Sep 2020 11:56:29 +0200 [thread overview]
Message-ID: <20200924095629.GL27174@8bytes.org> (raw)
In-Reply-To: <e2186418-d4d6-e1f4-5eb4-3bfafb5cebb2@arm.com>
On Thu, Sep 24, 2020 at 10:36:47AM +0100, Robin Murphy wrote:
> Yes, the issue was introduced by one of the changes in "dma-mapping:
> introduce DMA range map, supplanting dma_pfn_offset", so it only existed in
> the dma-mapping/for-next branch anyway.
Okay, alright then.
next prev parent reply other threads:[~2020-09-24 9:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 13:20 arm-smmu 5000000.iommu: Cannot accommodate DMA offset for IOMMU page tables Naresh Kamboju
2020-09-21 14:51 ` Robin Murphy
2020-09-24 9:03 ` Joerg Roedel
2020-09-24 9:08 ` Robin Murphy
2020-09-24 9:25 ` Joerg Roedel
2020-09-24 9:36 ` Robin Murphy
2020-09-24 9:56 ` Joerg Roedel [this message]
2020-10-09 13:54 ` Naresh Kamboju
2020-10-09 13:56 ` Naresh Kamboju
2020-10-10 18:53 ` Stephen Rothwell
2020-10-11 20:36 ` Jim Quinlan
2020-10-11 21:59 ` Florian Fainelli
2020-10-14 12:28 ` Fabio Estevam
2020-10-14 12:58 ` Miquel Raynal
2020-10-15 7:48 ` Christoph Hellwig
2020-10-15 18:17 ` Florian Fainelli
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=20200924095629.GL27174@8bytes.org \
--to=joro@8bytes.org \
--cc=Zhiqiang.Hou@nxp.com \
--cc=arnd@arndb.de \
--cc=iommu@lists.linux-foundation.org \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=masonccyang@mxic.com.tw \
--cc=miquel.raynal@bootlin.com \
--cc=naresh.kamboju@linaro.org \
--cc=poonam.aggrwal@nxp.com \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=suram@nxp.com \
--cc=will@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).