From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Albert Esteve <aesteve@redhat.com>, qemu-devel@nongnu.org
Cc: stefanha@gmail.com, "Michael S. Tsirkin" <mst@redhat.com>,
marcandre.lureau@gmail.com, kraxel@redhat.com,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH v3 3/3] hw/virtio: rename virtio dmabuf API
Date: Tue, 9 Jan 2024 22:14:44 +0100 [thread overview]
Message-ID: <6b7963ef-ce40-42a9-bfcf-26fadba562cb@linaro.org> (raw)
In-Reply-To: <20240109125614.220293-4-aesteve@redhat.com>
On 9/1/24 13:56, Albert Esteve wrote:
> Functions in the virtio-dmabuf module
> start with 'virtio_*', which is too
> generic and may not correctly identify
> them as part of the virtio dmabuf API.
>
> Rename all functions to 'virtio_dmabuf_*'
> instead to avoid confusion.
>
> Signed-off-by: Albert Esteve <aesteve@redhat.com>
> Acked-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> hw/display/virtio-dmabuf.c | 14 ++++----
> hw/virtio/vhost-user.c | 14 ++++----
> include/hw/virtio/virtio-dmabuf.h | 33 +++++++++---------
> tests/unit/test-virtio-dmabuf.c | 58 +++++++++++++++----------------
> 4 files changed, 60 insertions(+), 59 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2024-01-09 21:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 12:56 [PATCH v3 0/3] Virtio dmabuf improvements Albert Esteve
2024-01-09 12:56 ` [PATCH v3 1/3] hw/virtio: check owner for removing objects Albert Esteve
2024-02-05 12:57 ` Alex Bennée
2024-02-15 9:37 ` Albert Esteve
2024-01-09 12:56 ` [PATCH v3 2/3] hw/virtio: cleanup shared resources Albert Esteve
2024-02-05 23:11 ` Alex Bennée
2024-02-15 9:45 ` Albert Esteve
2024-02-15 11:41 ` Alex Bennée
2024-02-19 10:45 ` Albert Esteve
2024-02-19 12:07 ` Albert Esteve
2024-01-09 12:56 ` [PATCH v3 3/3] hw/virtio: rename virtio dmabuf API Albert Esteve
2024-01-09 21:14 ` Philippe Mathieu-Daudé [this message]
2024-02-05 9:58 ` [PATCH v3 0/3] Virtio dmabuf improvements Albert Esteve
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=6b7963ef-ce40-42a9-bfcf-26fadba562cb@linaro.org \
--to=philmd@linaro.org \
--cc=aesteve@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@redhat.com \
/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).