From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
Marek Szyprowski <m.szyprowski@samsung.com>,
Christoph Hellwig <hch@lst.de>,
Robin Murphy <robin.murphy@arm.com>,
Shanker Donthineni <sdonthineni@nvidia.com>,
Oreoluwa Babatunde <oreoluwa.babatunde@oss.qualcomm.com>
Subject: [GIT PULL] dma-mapping fix for Linux 6.17
Date: Thu, 28 Aug 2025 11:11:32 +0200 [thread overview]
Message-ID: <20250828091132.860125-1-m.szyprowski@samsung.com> (raw)
In-Reply-To: <CGME20250828091145eucas1p2293261860e89a33ae54ce1c908ef8619@eucas1p2.samsung.com>
The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/mszyprowski/linux.git tags/dma-mapping-6.17-2025-08-28
for you to fetch changes up to 89a2d212bdb4bc29bed8e7077abe054b801137ea:
dma/pool: Ensure DMA_DIRECT_REMAP allocations are decrypted (2025-08-13 11:02:10 +0200)
----------------------------------------------------------------
dma-mapping fixes for Linux 6.17
- another small fix relevant to arm64 systems with memory encryption
(Shanker Donthineni)
- fix relevant to arm32 systems with non-standard CMA configuration
(Oreoluwa Babatunde)
----------------------------------------------------------------
Oreoluwa Babatunde (1):
of: reserved_mem: Restructure call site for dma_contiguous_early_fixup()
Shanker Donthineni (1):
dma/pool: Ensure DMA_DIRECT_REMAP allocations are decrypted
drivers/of/of_reserved_mem.c | 16 ++++++++++++----
include/linux/dma-map-ops.h | 3 +++
kernel/dma/contiguous.c | 2 --
kernel/dma/pool.c | 4 ++--
4 files changed, 17 insertions(+), 8 deletions(-)
next parent reply other threads:[~2025-08-28 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250828091145eucas1p2293261860e89a33ae54ce1c908ef8619@eucas1p2.samsung.com>
2025-08-28 9:11 ` Marek Szyprowski [this message]
2025-08-29 16:39 ` pr-tracker-bot
[not found] <CGME20250909110159eucas1p260bd877535b4bc0d8fe6c3101f3dcbca@eucas1p2.samsung.com>
2025-09-09 11:01 ` Marek Szyprowski
2025-09-09 18:18 ` 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=20250828091132.860125-1-m.szyprowski@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=oreoluwa.babatunde@oss.qualcomm.com \
--cc=robin.murphy@arm.com \
--cc=sdonthineni@nvidia.com \
--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
all inboxes | Powered by JetHome®