From: Amneesh Singh <a-singh21@ti.com>
To: <sstabellini@kernel.org>
Cc: <boris.ostrovsky@oracle.com>, <hch@infradead.org>,
<iommu@lists.linux-foundation.org>, <jasowang@redhat.com>,
<jgross@suse.com>, <konrad.wilk@oracle.com>,
<linux-arm-kernel@lists.infradead.org>, <linux-imx@nxp.com>,
<linux-kernel@vger.kernel.org>, <mst@redhat.com>,
<peng.fan@nxp.com>, <virtualization@lists.linux-foundation.org>,
<x86@kernel.org>, <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] xen: introduce xen_vring_use_dma
Date: Tue, 30 Jul 2024 16:29:10 +0530 [thread overview]
Message-ID: <20240730105910.443753-1-a-singh21@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2007151001140.4124@sstabellini-ThinkPad-T480s>
Hi Stefano,
First off, apologies for bumping this dead thread.
I came across this patch signed off by you recently
https://github.com/Xilinx/linux-xlnx/commit/72cb5514953be3aa2ac00c57c9eaa100ecc67176
and was wondering if a patch replacing xen_domain() with xen_pv_domain() in
vring_use_dma_api() can be sent upstream? If not, is there a reason why?
Regards
Amneesh
next prev parent reply other threads:[~2024-07-30 10:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 9:17 Peng Fan
2020-06-24 9:06 ` Michael S. Tsirkin
2020-06-24 17:59 ` Stefano Stabellini
2020-06-24 20:47 ` Michael S. Tsirkin
2020-06-24 21:53 ` Stefano Stabellini
2020-06-24 22:16 ` Michael S. Tsirkin
2020-06-25 17:31 ` Stefano Stabellini
2020-06-26 15:32 ` Michael S. Tsirkin
2020-06-29 3:05 ` Peng Fan
2020-06-29 6:21 ` Michael S. Tsirkin
2020-06-29 6:25 ` Peng Fan
2020-06-29 6:33 ` Michael S. Tsirkin
2020-06-29 6:35 ` Peng Fan
2020-06-29 23:49 ` Stefano Stabellini
2020-06-30 1:40 ` Peng Fan
2020-06-29 23:46 ` Stefano Stabellini
2020-07-01 13:34 ` Christoph Hellwig
2020-07-01 17:34 ` Stefano Stabellini
2020-07-01 20:47 ` Michael S. Tsirkin
2020-07-01 21:23 ` Michael S. Tsirkin
2020-07-10 17:23 ` Stefano Stabellini
2020-07-11 18:44 ` Michael S. Tsirkin
2020-07-15 17:06 ` Stefano Stabellini
2024-07-30 10:59 ` Amneesh Singh [this message]
2024-07-30 22:29 ` Stefano Stabellini
2020-07-13 1:53 ` Peng Fan
2020-06-29 3:00 ` Peng Fan
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=20240730105910.443753-1-a-singh21@ti.com \
--to=a-singh21@ti.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jasowang@redhat.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=peng.fan@nxp.com \
--cc=sstabellini@kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®