From: "Michael S. Tsirkin" <mst@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: iommu@lists.linux.dev,
Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Bingbu Cao <bingbu.cao@intel.com>,
Jason Wang <jasowang@redhat.com>,
linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org,
linux-parisc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-s390@vger.kernel.org, sparclinux@vger.kernel.org,
linux-media@vger.kernel.org, virtualization@lists.linux.dev,
xen-devel@lists.xenproject.org
Subject: Re: clearly mark DMA_OPS support as an architecture feature v2
Date: Tue, 3 Sep 2024 05:39:39 -0400 [thread overview]
Message-ID: <20240903053917-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240903072744.GA2082@lst.de>
On Tue, Sep 03, 2024 at 09:27:44AM +0200, Christoph Hellwig wrote:
> 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.
Missed patch 1, I was wondering why I'm CC'd. Looks good, thanks.
prev parent reply other threads:[~2024-09-03 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 6:10 clearly mark DMA_OPS support as an architecture feature v2 Christoph Hellwig
2024-08-28 6:10 ` [PATCH 1/2] vdpa_sim: don't select DMA_OPS Christoph Hellwig
2024-09-03 9:39 ` Michael S. Tsirkin
2024-08-28 6:10 ` [PATCH 2/2] dma-mapping: clearly mark DMA ops as an architecture feature Christoph Hellwig
2024-08-28 6:21 ` Andreas Larsson
2024-08-29 4:30 ` Christoph Hellwig
2024-09-03 7:27 ` clearly mark DMA_OPS support as an architecture feature v2 Christoph Hellwig
2024-09-03 9:39 ` Michael S. Tsirkin [this message]
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=20240903053917-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=bingbu.cao@intel.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=jasowang@redhat.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
--cc=sakari.ailus@linux.intel.com \
--cc=sparclinux@vger.kernel.org \
--cc=virtualization@lists.linux.dev \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.