From: Jim Quinlan via iommu <iommu@lists.linux-foundation.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: "open list:DMA MAPPING HELPERS"
<iommu@lists.linux-foundation.org>,
Kevin Cernekee <cernekee@gmail.com>,
"maintainer:BROADCOM BCM7XXX ARM ARCHITECTURE"
<bcm-kernel-feedback-list@broadcom.com>,
Christoph Hellwig <hch@lst.de>,
linux-mips@vger.kernel.org
Subject: Re: can we switch bmips to the generic dma ranges code
Date: Tue, 3 Nov 2020 13:28:12 -0500 [thread overview]
Message-ID: <CA+-6iNxASk9Z9MeU8KM7UX+oUquthAqOSwD8q-6poKmHVHr0KQ@mail.gmail.com> (raw)
In-Reply-To: <b7a673ca-db14-5b67-c1f4-068ed2b49bed@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 484 bytes --]
I'll get on it.
Jim
On Tue, Nov 3, 2020 at 12:42 PM Florian Fainelli <f.fainelli@gmail.com> wrote:
>
>
>
> On 11/3/2020 2:15 AM, Christoph Hellwig wrote:
> > Hi Florian and others,
> >
> > now that the generic DMA ranges code landed, can we switch bmips over
> > to it instead of duplicating the logic?
>
> This should be fine, I cannot easily test the 338x chips, however as far
> as PCIe goes, I believe Jim may have some older patches he can dig up
> for testing.
> --
> Florian
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4167 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
prev parent reply other threads:[~2020-11-03 18:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 10:15 can we switch bmips to the generic dma ranges code Christoph Hellwig
2020-11-03 17:42 ` Florian Fainelli
2020-11-03 18:28 ` Jim Quinlan via iommu [this message]
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=CA+-6iNxASk9Z9MeU8KM7UX+oUquthAqOSwD8q-6poKmHVHr0KQ@mail.gmail.com \
--to=iommu@lists.linux-foundation.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=cernekee@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=hch@lst.de \
--cc=james.quinlan@broadcom.com \
--cc=linux-mips@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).