Re: [PATCH v7 00/22] dma-mapping: Track shared DMA state through direct, pool and swiotlb paths
Aneesh Kumar K.V <[email protected]>
| Newsgroups | dev.linux.lists.linux-coco,dev.linux.lists.iommu,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-kernel,org.kernel.vger.linux-s390,org.ozlabs.lists.linuxppc-dev |
|---|---|
| Message-ID | <[email protected]> |
Marek Szyprowski <[email protected]> writes: > On 13.07.2026 21:43, Jason Gunthorpe wrote: >> On Tue, Jul 07, 2026 at 03:03:48PM +0200, Marek Szyprowski wrote: >>> I'm fine with merging on top of the topic branch and I assume that this >>> patchset is mature enough to give it a try in linux-next, but first I >>> would like to get a review or at least acks from others with good CC >>> knowledge or experience. >> I think it is good to go from a CC perspective, there are still some >> more items to fix up (like the MMIO) but I'd rather they be followups >> at this point. > > Great. Aneesh, any chance You could send v8 with the remaining items > fixed till end of this week? I will be happy to push it to > dma-mapping-for-next for testing in linux-next asap. > Sure. You need this rebased on top of the pKVM changes, right? Otherwise, we'll end up with conflicts when you do the final pull request. -aneesh