From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtio@lists.oasis-open.org, virtio-dev@lists.oasis-open.org
Subject: Re: [virtio] [PATCH v3] conformance: clarify transitional/non-transitional
Date: Mon, 11 Mar 2019 17:49:07 +0100 [thread overview]
Message-ID: <20190311174907.0b5a9127.cohuck@redhat.com> (raw)
In-Reply-To: <20190311160018.29995-1-mst@redhat.com>
On Mon, 11 Mar 2019 12:00:46 -0400
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> Clarify that:
> - non-transitional just satisfy 3 main clauses
> - transitional also has a legacy interface:
> however note that it's not an optional component
> *for transitional devices* so MAY is inappropriate
> - legacy device descriptions are non-normative.
> In fact virtio 0.9 is non-normative as a whole
> and always was by design: it was early days and
> spec evolved to document bugs in implementations.
>
> VIRTIO-167
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
>
> Changes from v1:
> address remaining comments by Cornelia
> Changes from v1:
> address comments by Cornelia
>
> conformance.tex | 26 ++++++++++++++++++--------
> 1 file changed, 18 insertions(+), 8 deletions(-)
>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
next prev parent reply other threads:[~2019-03-11 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 16:00 [virtio] [PATCH v3] conformance: clarify transitional/non-transitional Michael S. Tsirkin
2019-03-11 16:49 ` Cornelia Huck [this message]
2019-03-12 15:00 ` [virtio] Re: [virtio-dev] " Halil Pasic
2019-03-12 16:04 ` Michael S. Tsirkin
2019-03-12 16:35 ` Halil Pasic
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=20190311174907.0b5a9127.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=virtio-dev@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