From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, virtio@lists.oasis-open.org
Subject: Re: [virtio-comment] [PATCH] packed-ring.tex: link conformance statements
Date: Tue, 19 Apr 2022 12:33:57 -0400 [thread overview]
Message-ID: <20220419123322-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <878rs185vw.fsf@redhat.com>
On Tue, Apr 19, 2022 at 05:11:47PM +0200, Cornelia Huck wrote:
> On Tue, Apr 19 2022, "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
> > Link conformance statements into conformance chapter.
> >
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> > conformance.tex | 9 +++++++++
> > packed-ring.tex | 16 +++++-----------
> > 2 files changed, 14 insertions(+), 11 deletions(-)
> >
> > diff --git a/conformance.tex b/conformance.tex
> > index 9807c30..663e7c3 100644
> > --- a/conformance.tex
> > +++ b/conformance.tex
> > @@ -85,6 +85,12 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
> > \item \ref{drivernormative:Basic Facilities of a Virtio Device / Virtqueues / Available Buffer Notification Suppression}
> > \item \ref{drivernormative:Basic Facilities of a Virtio Device / Virtqueues / Supplying Buffers to The Device / Updating idx}
> > \item \ref{drivernormative:Basic Facilities of a Virtio Device / Virtqueues / Supplying Buffers to The Device / Notifying The Device}
> > +\item \ref{drivernormative:Basic Facilities of a Virtio Device / Packed Virtqueues}
> > +\item \ref{drivernormative:Basic Facilities of a Virtio Device / PAcked Virtqueues / The Virtqueue Descriptor Table}
>
> I wonder whether we could use the opportunity to fix that "PAcked" typo
> here as well.
It's just a ref but if you like it, sure, make it a patch on top.
> > +\item \ref{drivernormative:Basic Facilities of a Virtio Device / Packed Virtqueues / Scatter-Gather Support}
> > +\item \ref{drivernormative:Basic Facilities of a Virtio Device / Packed Virtqueues / The Virtqueue Descriptor Table / Indirect Descriptors}
> > +\item \ref{drivernormative:Basic Facilities of a Virtio Device / Packed Virtqueues / Supplying Buffers to The Device / Updating flags}
> > +\item \ref{drivernormative:Basic Facilities of a Virtio Device / Packed Virtqueues / Supplying Buffers to The Device / Sending Available Buffer Notifications}
> > \item \ref{drivernormative:General Initialization And Device Operation / Device Initialization}
> > \item \ref{drivernormative:General Initialization And Device Operation / Device Cleanup}
> > \item \ref{drivernormative:Reserved Feature Bits}
> > @@ -340,6 +346,9 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
> > \item \ref{devicenormative:Basic Facilities of a Virtio Device / Virtqueues / Used Buffer Notification Suppression}
> > \item \ref{devicenormative:Basic Facilities of a Virtio Device / Virtqueues / The Virtqueue Used Ring}
> > \item \ref{devicenormative:Basic Facilities of a Virtio Device / Virtqueues / Available Buffer Notification Suppression}
> > +\item \ref{devicenormative:Basic Facilities of a Virtio Device / Packed Virtqueues}
> > +\item \ref{devicenormative:Basic Facilities of a Virtio Device / Packed Virtqueues / The Virtqueue Descriptor Table}
> > +\item \ref{devicenormative:Basic Facilities of a Virtio Device / Packed Virtqueues / Scatter-Gather Support}
> > \item \ref{devicenormative:Basic Facilities of a Virtio Device / Shared Memory Regions}
> > \item \ref{devicenormative:Reserved Feature Bits}
> > \end{itemize}
>
> I guess it is ok to link this up as an editorial update; the statements
> are pre-existing, and an implementation that does not know the feature
> bit remains compliant.
I agree.
--
MST
next prev parent reply other threads:[~2022-04-19 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 14:34 [virtio-comment] [PATCH] packed-ring.tex: link conformance statements Michael S. Tsirkin
2022-04-19 15:11 ` [virtio] " Cornelia Huck
2022-04-19 16:33 ` Michael S. Tsirkin [this message]
2022-04-20 11:57 ` [virtio-dev] " Halil Pasic
2022-04-20 10:02 ` [virtio] " Cornelia Huck
2022-04-20 17:59 ` Michael S. Tsirkin
2022-04-21 7:26 ` Cornelia Huck
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=20220419123322-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--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