From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: hch@lst.de, linux@armlinux.org.uk,
linux-arm-kernel@lists.infradead.org, m.szyprowski@samsung.com,
arnd@kernel.org, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] More ARM DMA ops cleanup
Date: Thu, 21 Apr 2022 16:13:00 +0200 [thread overview]
Message-ID: <20220421141300.GC20492@lst.de> (raw)
In-Reply-To: <cover.1650539846.git.robin.murphy@arm.com>
On Thu, Apr 21, 2022 at 12:36:56PM +0100, Robin Murphy wrote:
> Hi all,
>
> Thanks to Christoph's latest series, I'm reminded that, if we're going
> to give the ARM DMA ops some cleanup this cycle, it's as good a time as
> any to dust off these old patches and add them on top as well. I've
> based these on the arm-dma-direct branch which I assume matches the
> patches posted at [1].
All these do look sensible to me. But weren't you working on replacing
the ARM iommu dma_ops with dma-іommu anyway?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-04-21 14:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 11:36 [PATCH 0/3] More ARM DMA ops cleanup Robin Murphy
2022-04-21 11:36 ` [PATCH 1/3] ARM/dma-mapping: Drop .dma_supported for IOMMU ops Robin Murphy
2022-04-21 11:36 ` [PATCH 2/3] ARM/dma-mapping: Consolidate IOMMU ops callbacks Robin Murphy
2022-04-21 11:36 ` [PATCH 3/3] ARM/dma-mapping: Merge IOMMU ops Robin Murphy
2022-04-21 14:13 ` Christoph Hellwig [this message]
2022-04-21 14:35 ` [PATCH 0/3] More ARM DMA ops cleanup Robin Murphy
2022-08-27 12:24 ` Yongqin Liu
2022-08-30 9:48 ` Robin Murphy
2022-08-30 15:19 ` Yongqin Liu
2022-08-30 15:36 ` Robin Murphy
2022-08-30 15:44 ` Russell King (Oracle)
2022-08-31 16:41 ` Yongqin Liu
2022-08-31 17:09 ` Robin Murphy
2022-09-01 2:04 ` Yongqin Liu
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=20220421141300.GC20492@lst.de \
--to=hch@lst.de \
--cc=arnd@kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
/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).