From: "Michael S. Tsirkin" <mst@redhat.com>
To: Albert Esteve <aesteve@redhat.com>
Cc: qemu-devel@nongnu.org, kraxel@redhat.com,
marcandre.lureau@gmail.com, cohuck@redhat.com,
Fam Zheng <fam@euphon.net>
Subject: Re: [PATCH v3 0/4] Virtio shared dma-buf
Date: Wed, 21 Jun 2023 16:25:49 -0400 [thread overview]
Message-ID: <20230621162415-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CADSE00KNb4vxsL-JzQMrVgks+EJvt1dj7v9jd3s9gnkzGow6UA@mail.gmail.com>
On Wed, Jun 21, 2023 at 10:20:25AM +0200, Albert Esteve wrote:
> Hi!
>
> It has been a month since I sent this patch, so I'll give it a bump to get some
> attention back.
>
> @mst and @Fam any comments? What would be the next steps to take to move this
> forward?
>
> BR,
> Albert
>
>
I'd really want help from Gerd here. Don't know enough about dmabuf.
Gerd any comments or I'll just merge?
--
MST
next prev parent reply other threads:[~2023-06-21 20:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 9:13 [PATCH v3 0/4] Virtio shared dma-buf Albert Esteve
2023-05-24 9:13 ` [PATCH v3 1/4] uuid: add hash_func and equal_func Albert Esteve
2023-05-24 9:13 ` [PATCH v3 2/4] virtio-dmabuf: introduce virtio-dmabuf Albert Esteve
2023-05-24 9:13 ` [PATCH v3 3/4] vhost-user: add shared_object msg Albert Esteve
2023-06-22 19:57 ` Michael S. Tsirkin
2023-06-22 20:18 ` Marc-André Lureau
2023-06-23 7:45 ` Albert Esteve
2023-06-23 6:45 ` Michael S. Tsirkin
2023-06-23 7:19 ` Albert Esteve
2023-06-23 7:32 ` Michael S. Tsirkin
2023-06-23 13:46 ` Albert Esteve
2023-06-23 8:14 ` Michael S. Tsirkin
2023-06-23 12:08 ` Albert Esteve
2023-05-24 9:13 ` [PATCH v3 4/4] vhost-user: refactor send_resp code Albert Esteve
2023-06-23 6:48 ` Michael S. Tsirkin
2023-06-21 8:20 ` [PATCH v3 0/4] Virtio shared dma-buf Albert Esteve
2023-06-21 20:25 ` Michael S. Tsirkin [this message]
2023-06-22 19:53 ` Michael S. Tsirkin
2023-06-23 6:49 ` Michael S. Tsirkin
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=20230621162415-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=aesteve@redhat.com \
--cc=cohuck@redhat.com \
--cc=fam@euphon.net \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).