All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] [PATCH 1/3] conformance: make driver conformance list easier to read and maintain
Date: Tue, 19 May 2020 08:57:44 +0200	[thread overview]
Message-ID: <20200519085744.17bd65f6.cohuck@redhat.com> (raw)
In-Reply-To: <20200515132751.62332-2-david@redhat.com>

On Fri, 15 May 2020 15:27:49 +0200
David Hildenbrand <david@redhat.com> wrote:

> Let's define it just like the device conformance list.
> 
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
>  conformance.tex | 12 +++++++++++-
>  1 file changed, 11 insertions(+), 1 deletion(-)
> 
> diff --git a/conformance.tex b/conformance.tex
> index b6fdec0..ed7d77f 100644
> --- a/conformance.tex
> +++ b/conformance.tex
> @@ -15,7 +15,17 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
>    \begin{itemize}
>      \item Clause \ref{sec:Conformance / Driver Conformance}.
>      \item One of clauses \ref{sec:Conformance / Driver Conformance / PCI Driver Conformance}, \ref{sec:Conformance / Driver Conformance / MMIO Driver Conformance} or \ref{sec:Conformance / Driver Conformance / Channel I/O Driver Conformance}.
> -    \item One of clauses \ref{sec:Conformance / Driver Conformance / Network Driver Conformance}, \ref{sec:Conformance / Driver Conformance / Block Driver Conformance}, \ref{sec:Conformance / Driver Conformance / Console Driver Conformance}, \ref{sec:Conformance / Driver Conformance / Entropy Driver Conformance}, \ref{sec:Conformance / Driver Conformance / Traditional Memory Balloon Driver Conformance}, \ref{sec:Conformance / Driver Conformance / SCSI Host Driver Conformance}, \ref{sec:Conformance / Driver Conformance / Input Driver Conformance}, \ref{sec:Conformance / Driver Conformance / Crypto Driver Conformance}, \ref{sec:Conformance / Driver Conformance / Socket Driver Conformance} or \ref{sec:Conformance / Driver Conformance / IOMMU Driver Conformance}.
> +    \item One of clauses
> +\ref{sec:Conformance / Driver Conformance / Network Driver Conformance},
> +\ref{sec:Conformance / Driver Conformance / Block Driver Conformance},
> +\ref{sec:Conformance / Driver Conformance / Console Driver Conformance},
> +\ref{sec:Conformance / Driver Conformance / Entropy Driver Conformance},
> +\ref{sec:Conformance / Driver Conformance / Traditional Memory Balloon Driver Conformance},
> +\ref{sec:Conformance / Driver Conformance / SCSI Host Driver Conformance},
> +\ref{sec:Conformance / Driver Conformance / Input Driver Conformance},
> +\ref{sec:Conformance / Driver Conformance / Crypto Driver Conformance},
> +\ref{sec:Conformance / Driver Conformance / Socket Driver Conformance} or
> +\ref{sec:Conformance / Driver Conformance / IOMMU Driver Conformance}.
>      \item Clause \ref{sec:Conformance / Legacy Interface: Transitional Device and Transitional Driver Conformance}.
>    \end{itemize}
>  \item[Device] A device MUST conform to four conformance clauses:

Looks much nicer.

Reviewed-by: Cornelia Huck <cohuck@redhat.com>


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/


  reply	other threads:[~2020-05-19  6:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 13:27 [virtio-comment] [PATCH 0/3] virtio-spec: Add virtio-mem device specification David Hildenbrand
2020-05-15 13:27 ` [virtio-comment] [PATCH 1/3] conformance: make driver conformance list easier to read and maintain David Hildenbrand
2020-05-19  6:57   ` Cornelia Huck [this message]
2020-05-15 13:27 ` [virtio-comment] [PATCH 2/3] conformance: Reference RPMB Driver Conformance David Hildenbrand
2020-05-19  6:58   ` Cornelia Huck
2020-05-15 13:27 ` [virtio-comment] [PATCH 3/3] Add virtio-mem device specification David Hildenbrand

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=20200519085744.17bd65f6.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=virtio-comment@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.