From: Cornelia Huck <cohuck@redhat.com>
To: virtio@lists.oasis-open.org, virtio-comment@lists.oasis-open.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [virtio-comment] Re: [PATCH] conformance: hook up GPU device normative statements
Date: Wed, 13 Apr 2022 11:36:32 +0200 [thread overview]
Message-ID: <87ilrd9vfj.fsf@redhat.com> (raw)
In-Reply-To: <20220408091213.38247-1-cohuck@redhat.com>
On Fri, Apr 08 2022, Cornelia Huck <cohuck@redhat.com> wrote:
> These statements already exist, but were not linked in the conformance section.
>
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> ---
>
> I think this one can go in as an editorial update, at it just seems
> to have been missed.
>
> However, I think we need to go over the GPU spec: it seems to have
> a lot of MUST etc. language that is not in any normative section.
> No driver normative sections also seem to point to some possible
> omissions. Probably 1.3 material, though.
>
> ---
> conformance.tex | 10 ++++++++++
> 1 file changed, 10 insertions(+)
Pushed as editorial update.
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
prev parent reply other threads:[~2022-04-13 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 9:12 [PATCH] conformance: hook up GPU device normative statements Cornelia Huck
2022-04-13 9:36 ` Cornelia Huck [this message]
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=87ilrd9vfj.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=kraxel@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio@lists.oasis-open.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