From: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
To: Dmitry Osipenko <dmitry.osipenko@collabora.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
Gurchetan Singh <gurchetansingh@chromium.org>,
Rob Clark <robdclark@gmail.com>, Huang Rui <ray.huang@amd.com>,
Sergio Lopez <slp@redhat.com>,
Akihiko Odaki <akihiko.odaki@daynix.com>,
virtio-comment@lists.linux.dev,
"Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v3 0/3] VirtIO-GPU spec improvements
Date: Wed, 26 Feb 2025 17:08:02 +0100 [thread overview]
Message-ID: <Z788Yrh6qy9dJOVP@fedora> (raw)
In-Reply-To: <de02684a-8f36-48ba-b505-85b6d74f5e8b@collabora.com>
On Wed, Feb 26, 2025 at 01:59:06PM +0300, Dmitry Osipenko wrote:
> On 7/19/24 15:06, Dmitry Osipenko wrote:
> > Hi,
> >
> > This is a repost of v2 to the new virtio-comment mailing list.
> > Michael Tsirkin suggested to repost the patches, here they are.
> >
> > Dmitry Osipenko (3):
> > virtio-gpu: Rename GFXSTREAM context capset to GFXSTREAM_VULKAN
> > virtio-gpu: Document VIRTIO_GPU_CAPSET_DRM
> > virtio-gpu: Update venus-protocol URL
> >
> > device-types/gpu/description.tex | 11 +++++++----
> > 1 file changed, 7 insertions(+), 4 deletions(-)
> >
>
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/182
>
I think what is missing is to explicitly request a vote as is explained
in 2) at
https://github.com/oasis-tcs/virtio-spec/blob/master/README.md#use-of-github-issues.
Thanks, Matias
next prev parent reply other threads:[~2025-02-26 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 12:06 [PATCH v3 0/3] VirtIO-GPU spec improvements Dmitry Osipenko
2024-07-19 12:06 ` [PATCH v3 1/3] virtio-gpu: Rename GFXSTREAM context capset to GFXSTREAM_VULKAN Dmitry Osipenko
2024-07-19 12:06 ` [PATCH v3 2/3] virtio-gpu: Document VIRTIO_GPU_CAPSET_DRM Dmitry Osipenko
2024-07-19 12:06 ` [PATCH v3 3/3] virtio-gpu: Update venus-protocol URL Dmitry Osipenko
2024-07-19 13:09 ` [PATCH v3 0/3] VirtIO-GPU spec improvements Gerd Hoffmann
2025-02-26 10:59 ` Dmitry Osipenko
2025-02-26 16:08 ` Matias Ezequiel Vara Larsen [this message]
2025-02-26 17:29 ` Michael S. Tsirkin
2025-02-26 19:38 ` Dmitry Osipenko
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=Z788Yrh6qy9dJOVP@fedora \
--to=mvaralar@redhat.com \
--cc=akihiko.odaki@daynix.com \
--cc=dmitry.osipenko@collabora.com \
--cc=gurchetansingh@chromium.org \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=ray.huang@amd.com \
--cc=robdclark@gmail.com \
--cc=slp@redhat.com \
--cc=virtio-comment@lists.linux.dev \
/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