From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: virtio@lists.oasis-open.org, virtio-dev@lists.oasis-open.org
Subject: Re: [virtio] [PATCH v2] conformance: clarify transitional/non-transitional
Date: Tue, 12 Mar 2019 12:11:32 -0400 [thread overview]
Message-ID: <20190312121018-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20190312170631.3f1a5118.cohuck@redhat.com>
On Tue, Mar 12, 2019 at 05:06:31PM +0100, Cornelia Huck wrote:
> On Tue, 12 Mar 2019 12:01:41 -0400
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
> > We already have a specification for conformance targets for
> > non-transitional devices.
> > Just add another clause that transitional devices satisfy.
> >
> > VIRTIO-167
> >
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> > conformance.tex | 8 ++------
> > 1 file changed, 2 insertions(+), 6 deletions(-)
> >
> > diff --git a/conformance.tex b/conformance.tex
> > index 6df113b..8b69e39 100644
> > --- a/conformance.tex
> > +++ b/conformance.tex
> > @@ -341,13 +341,9 @@ A conformant implementation MUST be either transitional or
> > non-transitional, see \ref{intro:Legacy
> > Interface: Terminology}.
> >
> > -A non-transitional implementation conforms to this specification
> > -if it satisfies all of the MUST or REQUIRED level requirements
> > -defined above.
> > -
> > -An implementation MAY choose to implement OPTIONAL support for the
> > +A transitional implementation MUST implement support for the
> > legacy interface, including support for legacy drivers
> > -or devices, by additionally conforming to all of the MUST or
> > +or devices, by conforming to all of the MUST or
> > REQUIRED level requirements for the legacy interface
> > for the transitional devices and drivers.
> >
>
> Wouldn't that be v4?
Donnu :(
> I'm currently very confused by the avalanche of patches and which issues
> they fix...
It could be easiest to follow links under ballots.
Each ballot is linked to the patch.
--
MST
---------------------------------------------------------------------
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-12 16:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 16:01 [virtio] [PATCH v2] conformance: clarify transitional/non-transitional Michael S. Tsirkin
2019-03-12 16:06 ` Cornelia Huck
2019-03-12 16:11 ` Michael S. Tsirkin [this message]
2019-03-13 1:47 ` [virtio] " Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2019-03-11 15:10 [virtio] " Michael S. Tsirkin
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=20190312121018-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@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