From: Halil Pasic <pasic@linux.vnet.ibm.com>
To: virtio@lists.oasis-open.org, virtio-dev@lists.oasis-open.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
Halil Pasic <pasic@linux.vnet.ibm.com>
Subject: [virtio] [PATCH v2 2/2] introduction: simplify the designation of legacy
Date: Tue, 13 Feb 2018 13:44:08 +0100 [thread overview]
Message-ID: <1518525848-8307-3-git-send-email-pasic@linux.vnet.ibm.com> (raw)
In-Reply-To: <1518525848-8307-1-git-send-email-pasic@linux.vnet.ibm.com>
The sentence designating the documents defining what later
became known as the legacy virtio interface had the most
important piece of information placed in parenthesis.
Let's reword this sentence so we avoid using an ambiguous designation
based on a relative anchor (i.e. 'earlier drafts of this specification')
and just use the absolute anchor (version 1.0).
VIRTIO-164
Signed-off-by: Halil Pasic <pasic@linux.vnet.ibm.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
---
introduction.tex | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/introduction.tex b/introduction.tex
index 979881e..78c340d 100644
--- a/introduction.tex
+++ b/introduction.tex
@@ -78,8 +78,8 @@ The key words ``MUST'', ``MUST NOT'', ``REQUIRED'', ``SHALL'', ``SHALL NOT'', ``
\subsection{Legacy Interface: Terminology}\label{intro:Legacy
Interface: Terminology}
-Earlier drafts of this specification (i.e. revisions before 1.0,
-see e.g. \hyperref[intro:Virtio PCI Draft]{[Virtio PCI Draft]})
+Specification drafts preceding version 1.0 of this specification
+(e.g. see \hyperref[intro:Virtio PCI Draft]{[Virtio PCI Draft]})
defined a similar, but different
interface between the driver and the device.
Since these are widely deployed, this specification
--
1.7.1
---------------------------------------------------------------------
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:[~2018-02-13 12:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 12:44 [virtio] [PATCH v2 0/2] two versioning related changes Halil Pasic
2018-02-13 12:44 ` [virtio] [PATCH v2 1/2] ccw: be more precise about the semantic of revision 1 Halil Pasic
2018-02-13 12:44 ` Halil Pasic [this message]
2018-02-13 14:41 ` [virtio] Re: [PATCH v2 0/2] two versioning related changes Michael S. Tsirkin
2018-02-13 16:27 ` Cornelia Huck
2018-02-28 15:56 ` Cornelia Huck
2018-02-28 16:25 ` 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=1518525848-8307-3-git-send-email-pasic@linux.vnet.ibm.com \
--to=pasic@linux.vnet.ibm.com \
--cc=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