From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: [GIT PULL] dma-mapping updates for 5.12
Date: Wed, 24 Feb 2021 08:46:01 +0100 [thread overview]
Message-ID: <YDYEOTIu02GKL8T2@infradead.org> (raw)
The following changes since commit 9f5f8ec50165630cfc49897410b30997d4d677b5:
dma-mapping: benchmark: use u8 for reserved field in uAPI structure (2021-02-05 12:48:46 +0100)
are available in the Git repository at:
git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-5.12
for you to fetch changes up to 81d88ce55092edf1a1f928efb373f289c6b90efd:
dma-mapping: remove the {alloc,free}_noncoherent methods (2021-02-09 18:01:38 +0100)
----------------------------------------------------------------
dma-mapping updates for 5.12:
- add support to emulate processing delays in the DMA API benchmark
selftest (Barry Song)
- remove support for non-contiguous noncoherent allocations,
which aren't used and will be replaced by a different API
----------------------------------------------------------------
Barry Song (1):
dma-mapping: benchmark: pretend DMA is transmitting
Christoph Hellwig (1):
dma-mapping: remove the {alloc,free}_noncoherent methods
Documentation/core-api/dma-api.rst | 64 +++++++++----------------
drivers/iommu/dma-iommu.c | 30 ------------
include/linux/dma-map-ops.h | 5 --
include/linux/dma-mapping.h | 17 +++++--
kernel/dma/map_benchmark.c | 12 ++++-
kernel/dma/mapping.c | 40 ----------------
tools/testing/selftests/dma/dma_map_benchmark.c | 21 ++++++--
7 files changed, 64 insertions(+), 125 deletions(-)
next reply other threads:[~2021-02-24 7:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 7:46 Christoph Hellwig [this message]
2021-02-24 18:46 ` [GIT PULL] dma-mapping updates for 5.12 pr-tracker-bot
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=YDYEOTIu02GKL8T2@infradead.org \
--to=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).