Hi Marek, On Fri, Jul 31, 2026 at 09:33:47AM +0200, Marek Szyprowski wrote: > On 25.07.2026 09:09, Aneesh Kumar K.V wrote: > > "Aneesh Kumar K.V (Arm)" <[email protected]> writes: > >> This series tracks confidential-computing shared DMA state through the > >> dma-direct, dma-pool, and swiotlb paths so that encrypted and decrypted > >> DMA buffers are handled consistently. > >> > >> Today, the direct DMA path mostly relies on force_dma_unencrypted() for > >> [...] > > pKVM topic branch is now available > > > > https://lore.kernel.org/all/[email protected]/ > > > > https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git > > for-next/coco > I've just got back from my holiday's and I see that there is everything ready > to give > this patchset some tests in linux-next. I hope nothing will break. > > I've applied this patchset to dma-mapping-for-next, on top of pKVM topic > branch with
I was trying to find this tree and it seems the MAINTAINERS file have the wrong address: DMA MAPPING HELPERS M: Marek Szyprowski <[email protected]> R: Robin Murphy <[email protected]> L: [email protected] S: Supported W: http://git.infradead.org/users/hch/dma-mapping.git T: git git://git.infradead.org/users/hch/dma-mapping.git I believe the corret one is: https://git.kernel.org/pub/scm/linux/kernel/git/mszyprowski/linux.git/ Thanks, Mostafa > patch "[PATCH v8 17/23] dma-direct: make dma_direct_map_phys() honor > DMA_ATTR_CC_SHARED" > rebased onto latest changes in arch/arm64/mm/init.c. > > The remaining items pointed in the review can be fixed incrementally. > > Best regards > -- > Marek Szyprowski, PhD > Samsung R&D Institute Poland >
