From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: virtio-return-3299-cohuck=redhat.com@lists.oasis-open.org Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Date: Tue, 12 Mar 2019 21:47:30 -0400 From: "Michael S. Tsirkin" Message-ID: <20190312214700-mutt-send-email-mst@kernel.org> References: <20190312160109.7077-1-mst@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190312160109.7077-1-mst@redhat.com> Subject: [virtio] Re: [PATCH v2] conformance: clarify transitional/non-transitional To: virtio@lists.oasis-open.org, virtio-dev@lists.oasis-open.org List-ID: On Tue, Mar 12, 2019 at 12:01:41PM -0400, Michael S. Tsirkin 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 Correction: this should be v4. Will repost with the correct version #. > --- > 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. > > -- > 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