public inbox for virtio-comment@lists.linux.dev
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: virtio-comment@lists.linux.dev
Cc: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
Subject: Re: [oasis-tcs/virtio-spec] Missing struct definitions in GPU device "5.7.6.9 Device Operation: controlq (3d)" (Issue #239)
Date: Mon, 16 Feb 2026 08:16:01 -0500	[thread overview]
Message-ID: <20260216081453-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <oasis-tcs/virtio-spec/issues/239@github.com>

On Mon, Feb 16, 2026 at 04:36:00AM -0800, Manos Pitsidianakis wrote:
> ●epilys created an issue (oasis-tcs/virtio-spec#239)
> 
> These structs are defined in Linux UAPI ^1 but not in the spec, is this an
> oversight or on purpose?
> 
> https://github.com/oasis-tcs/virtio-spec/blob/
> 1ba6e8108644d598cf9c772bac7b856fb5c7df6b/device-types/gpu/description.tex#
> L752-L767
> 
> Should I submit a patch to add these definitions?
> 
> Footnotes
> 
>  1. https://github.com/torvalds/linux/blob/
>     0f2acd3148e0ef42bdacbd477f90e8533f96b2ac/include/uapi/linux/virtio_gpu.h#
>     L296 ↩
> 
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you are subscribed to this thread.*Message ID: 
> <oasis-tcs/virtio-spec/issues/239@github.com>


Pls direct all spec comments to the virtio-comments mailing list.
Sending a patch is a great way to start a discussion. Thanks!


       reply	other threads:[~2026-02-16 13:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <oasis-tcs/virtio-spec/issues/239@github.com>
2026-02-16 13:16 ` Michael S. Tsirkin [this message]
2026-02-19  8:30   ` [oasis-tcs/virtio-spec] Missing struct definitions in GPU device "5.7.6.9 Device Operation: controlq (3d)" (Issue #239) Manos Pitsidianakis

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=20260216081453-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=manos.pitsidianakis@linaro.org \
    --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