From: Christoph Hellwig <hch@lst.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Tony Luck <tony.luck@intel.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>,
linux-ia64@vger.kernel.org, iommu@lists.linux-foundation.org,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: merge swiotlb support into dma_direct_ops
Date: Tue, 4 Dec 2018 08:16:40 -0800 [thread overview]
Message-ID: <20181204161645.8038-1-hch@lst.de> (raw)
Hi Konrad and others,
can you review this series? It merges the swiotlb support into the
DMA direct ops so that we don't have to duplicate the dma mapping logic
in multiple places.
Note that this is based on the dma_mapping_error series for which I'd
still like to collect a few more reviews, so pulling the git tree might
be easiest for testing.
The git tree is available here:
git://git.infradead.org/users/hch/misc.git swiotlb-merge
Gitweb:
http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/swiotlb-merge
next reply other threads:[~2018-12-04 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 16:16 Christoph Hellwig [this message]
2018-12-04 16:16 ` [PATCH 1/5] swiotlb: remove SWIOTLB_MAP_ERROR Christoph Hellwig
2018-12-04 16:16 ` [PATCH 2/5] swiotlb: remove dma_mark_clean Christoph Hellwig
2018-12-04 16:16 ` [PATCH 3/5] dma-direct: improve addressability error reporting Christoph Hellwig
2018-12-04 16:16 ` [PATCH 4/5] dma-direct: use dma_direct_map_page to implement dma_direct_map_sg Christoph Hellwig
2018-12-04 16:16 ` [PATCH 5/5] dma-direct: merge swiotlb_dma_ops into the dma_direct code Christoph Hellwig
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=20181204161645.8038-1-hch@lst.de \
--to=hch@lst.de \
--cc=fenghua.yu@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
--cc=tony.luck@intel.com \
--cc=x86@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
all inboxes | Powered by JetHome®