[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240903072744.GA2082@lst.de>
Date: Tue, 3 Sep 2024 09:27:44 +0200
From: Christoph Hellwig <hch@....de>
To: iommu@...ts.linux.dev
Cc: Marek Szyprowski <m.szyprowski@...sung.com>,
Robin Murphy <robin.murphy@....com>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
Bingbu Cao <bingbu.cao@...el.com>,
"Michael S . Tsirkin " <mst@...hat.com>,
Jason Wang <jasowang@...hat.com>, linux-kernel@...r.kernel.org,
linux-alpha@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mips@...r.kernel.org, linux-parisc@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, linux-s390@...r.kernel.org,
sparclinux@...r.kernel.org, linux-media@...r.kernel.org,
virtualization@...ts.linux.dev, xen-devel@...ts.xenproject.org
Subject: Re: clearly mark DMA_OPS support as an architecture feature v2
I've pulled this into the dma-mapping for-next tree, although I'd
love to see one of the vdpa maintainers look over patch 1. I'm
pretty sure it's correct, but a confirmation would be good.
Powered by blists - more mailing lists