From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Christoph Hellwig <hch@lst.de>,
iommu@lists.linux-foundation.org,
Marek Szyprowski <m.szyprowski@samsung.com>,
Paul Burton <paul.burton@mips.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] dma-mapping: move the dma_coherent flag to struct device
Date: Tue, 11 Sep 2018 08:48:02 +0200 [thread overview]
Message-ID: <20180911064802.GB6214@lst.de> (raw)
In-Reply-To: <aa6f49f8-24ea-f166-9c58-aecb13df0418@arm.com>
On Mon, Sep 10, 2018 at 05:06:40PM +0100, Robin Murphy wrote:
>>> Nits aside, this otherwise looks sane to me for factoring out the
>>> equivalent Xen and arm64 DMA ops cases.
>>
>> Like this? :)
>>
>> http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/dma-maybe-coherent
>
> Man, that's going to take me a *lot* of time to pick through. All those
> horrendous subtleties that I barely remember!
The good thing is that if I remember correctly there is just a single
patch that (intentionally) changes behavior. The rest is just
refactoring and moving code around.
Anyway, I want to get this series in now, and the kick off the swiotlb
discussion with Konread. We might not even get to the iommu patches
for this merge window depending on how long it takes.
next prev parent reply other threads:[~2018-09-11 6:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 6:05 merge dma_direct_ops and dma_noncoherent_ops v2 Christoph Hellwig
2018-09-10 6:05 ` Christoph Hellwig
2018-09-10 6:05 ` [PATCH 1/5] MIPS: don't select DMA_MAYBE_COHERENT from DMA_PERDEV_COHERENT Christoph Hellwig
2018-09-10 6:05 ` Christoph Hellwig
2018-09-10 6:05 ` [PATCH 2/5] dma-mapping: move the dma_coherent flag to struct device Christoph Hellwig
2018-09-10 6:05 ` Christoph Hellwig
2018-09-10 15:19 ` Robin Murphy
2018-09-10 15:47 ` Christoph Hellwig
2018-09-10 16:06 ` Robin Murphy
2018-09-10 16:06 ` Robin Murphy
2018-09-11 6:48 ` Christoph Hellwig [this message]
2018-09-11 6:58 ` Christoph Hellwig
2018-09-10 16:13 ` Greg Kroah-Hartman
2018-09-11 6:46 ` Christoph Hellwig
2018-09-11 6:46 ` Christoph Hellwig
2018-09-11 8:19 ` Greg Kroah-Hartman
2018-09-11 8:19 ` Greg Kroah-Hartman
2018-09-10 6:05 ` [PATCH 3/5] dma-mapping: merge direct and noncoherent ops Christoph Hellwig
2018-09-10 6:05 ` [PATCH 4/5] dma-mapping: consolidate the dma mmap implementations Christoph Hellwig
2018-09-10 6:05 ` Christoph Hellwig
2018-09-10 6:05 ` [PATCH 5/5] dma-mapping: support non-coherent devices in dma_common_get_sgtable Christoph Hellwig
2018-09-10 6:05 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2018-08-27 14:50 Christoph Hellwig
2018-08-27 14:50 ` [PATCH 2/5] dma-mapping: move the dma_coherent flag to struct device Christoph Hellwig
2018-08-31 20:11 ` Paul Burton
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=20180911064802.GB6214@lst.de \
--to=hch@lst.de \
--cc=gregkh@linuxfoundation.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=m.szyprowski@samsung.com \
--cc=paul.burton@mips.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 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.