[PATCH v8 00/23] dma-mapping: Track shared DMA state through direct, pool and swiotlb paths

[Marek Szyprowski]

On 07.08.2026 11:51, Mostafa Saleh wrote:
> 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)" <aneesh.kumar at kernel.org> 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/178467286876.125042.12010461715645610054.b4-ty@kernel.org/
>>>
>>> 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 <m.szyprowski at samsung.com>
> R:      Robin Murphy <robin.murphy at arm.com>
> L:      iommu at lists.linux.dev
> S:      Supported
> W:      https://protect2.fireeye.com/v1/url?k=dbfa7485-ba7161ce-dbfbffca-74fe485fb305-800153ec5c55b6a1&q=1&e=ed464763-9bbc-4c24-9629-f9ac5e8f5ef4&u=http%3A%2F%2Fgit.infradead.org%2Fusers%2Fhch%2Fdma-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 for pointing this out! It looks that I've forgot to update it.I will send an update soon.

Best regards
-- 
Marek Szyprowski, PhD
Samsung R&D Institute Poland