Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Halil Pasic <pasic@linux.vnet.ibm.com>
Cc: virtio@lists.oasis-open.org, virtio-dev@lists.oasis-open.org,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: [virtio] Re: [PATCH 2/2] introduction: simplify the designation of legacy
Date: Mon, 12 Feb 2018 14:00:24 +0100	[thread overview]
Message-ID: <20180212140024.356a869d.cohuck@redhat.com> (raw)
In-Reply-To: <1518206354-29610-3-git-send-email-pasic@linux.vnet.ibm.com>

On Fri,  9 Feb 2018 20:59:14 +0100
Halil Pasic <pasic@linux.vnet.ibm.com> wrote:

> 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).
> 
> Signed-off-by: Halil Pasic <pasic@linux.vnet.ibm.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

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

---------------------------------------------------------------------
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 


  reply	other threads:[~2018-02-12 13:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09 19:59 [virtio] [PATCH 0/2] two versioning related changes Halil Pasic
2018-02-09 19:59 ` [virtio] [PATCH 1/2] ccw: be more precise the semantic of revision 1 Halil Pasic
2018-02-12 12:59   ` [virtio] " Cornelia Huck
2018-02-12 14:25     ` [virtio] Re: [virtio-dev] " Halil Pasic
2018-02-12 21:09       ` Michael S. Tsirkin
2018-02-12 22:47         ` Halil Pasic
2018-02-09 19:59 ` [virtio] [PATCH 2/2] introduction: simplify the designation of legacy Halil Pasic
2018-02-12 13:00   ` Cornelia Huck [this message]
2018-02-09 20:43 ` [virtio] Re: [PATCH 0/2] two versioning related changes Michael S. Tsirkin
2018-02-12 13:03   ` Cornelia Huck
2018-02-12 14:29     ` 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=20180212140024.356a869d.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=mst@redhat.com \
    --cc=pasic@linux.vnet.ibm.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