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.8, part 2
Date: Sat, 6 Jun 2020 18:09:32 +0200 [thread overview]
Message-ID: <20200606160932.GB3482728@infradead.org> (raw)
These were in a separate stable branch so that various media and drm
trees could pull the in for bug fixes, but looking at linux-next that
hasn't actually happened yet. Still sending the APIs to you in the
hope that these bug fixes get picked up for 5.8 in one way or another.
The following changes since commit 24085f70a6e1b0cb647ec92623284641d8270637:
Merge tag 'trace-v5.7-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace (2020-05-12 11:06:26 -0700)
are available in the Git repository at:
git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-5.8-2
for you to fetch changes up to 48530d9fab0d3bf08827f9167be54acf66d4d457:
iommu: add generic helper for mapping sgtable objects (2020-05-13 15:48:20 +0200)
----------------------------------------------------------------
dma-mapping updates for 5.8, part 2
- add DMA mapping helpers for struct sg_table (Marek Szyprowski)
----------------------------------------------------------------
Marek Szyprowski (3):
dma-mapping: add generic helpers for mapping sgtable objects
scatterlist: add generic wrappers for iterating over sgtable objects
iommu: add generic helper for mapping sgtable objects
include/linux/dma-mapping.h | 80 +++++++++++++++++++++++++++++++++++++++++++++
include/linux/iommu.h | 16 +++++++++
include/linux/scatterlist.h | 50 ++++++++++++++++++++++++++--
3 files changed, 143 insertions(+), 3 deletions(-)
next reply other threads:[~2020-06-06 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 16:09 Christoph Hellwig [this message]
2020-06-06 19:15 ` [GIT PULL] dma-mapping updates for 5.8, part 2 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=20200606160932.GB3482728@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).