From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: [GIT PULL] dma-mapping fixes for Linux 6.12
Date: Tue, 24 Sep 2024 08:25:53 +0200 [thread overview]
Message-ID: <ZvJbcRLlblu7s2kd@infradead.org> (raw)
The following changes since commit 88264981f2082248e892a706b2c5004650faac54:
Merge tag 'sched_ext-for-6.12' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext (2024-09-21 09:44:57 -0700)
are available in the Git repository at:
git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-6.12-2024-09-24
for you to fetch changes up to b348b6d17fd1d5d89b86db602f02bea54a754bd8:
dma-mapping: report unlimited DMA addressing in IOMMU DMA path (2024-09-23 08:38:56 +0200)
----------------------------------------------------------------
dma-mapping fixes for Linux 6.12
- sort out a few issues with the direct calls to iommu-dma
(Christoph Hellwig, Leon Romanovsky)
----------------------------------------------------------------
Christoph Hellwig (2):
dma-mapping: fix vmap and mmap of noncontiougs allocations
iommu/dma: remove most stubs in iommu-dma.h
Leon Romanovsky (1):
dma-mapping: report unlimited DMA addressing in IOMMU DMA path
drivers/iommu/dma-iommu.c | 33 +++++++++++++
include/linux/dma-map-ops.h | 19 --------
include/linux/iommu-dma.h | 114 ++++++--------------------------------------
kernel/dma/mapping.c | 43 ++++++-----------
4 files changed, 62 insertions(+), 147 deletions(-)
next reply other threads:[~2024-09-24 6:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 6:25 Christoph Hellwig [this message]
2024-09-24 19:36 ` [GIT PULL] dma-mapping fixes for Linux 6.12 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-09-29 6:11 Christoph Hellwig
2024-09-29 17:04 ` 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=ZvJbcRLlblu7s2kd@infradead.org \
--to=hch@infradead.org \
--cc=iommu@lists.linux.dev \
--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