Re: [virtio-dev] [PATCH 3/6] ccw: map common notifications terminology to ccw

[Stefan Hajnoczi <stefanha@redhat.com>]

On Thu, Apr 26, 2018 at 12:59:59PM +0200, Halil Pasic wrote:
> The various notifications are introduced and specified in the common
> (i.e. transport agnostic) portion of this specification. How
> notifications are realised for a given transport is something each
> transport has to specify.
> 
> Let's make the relationship between the virtio-ccw terms and the common
> terms more obvious.
> 
> Signed-off-by: Halil Pasic <pasic@linux.ibm.com>
> ---
> Changelog:
> * implemented Connie's suggestions (typos, grammar)
> * avoided 'realized using virtual interrupts'
> ---
>  content.tex |   42 ++++++++++++++++++++++++++++++++++++++++++
>  1 files changed, 42 insertions(+), 0 deletions(-)
> 
> diff --git a/content.tex b/content.tex
> index d7e2b18..e5b2499 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -1943,6 +1943,18 @@ Bytes & Description & Contents \\
>  \hline
>  \end{tabular}
>  
> +A virtio-ccw proxy device facilitates:
> +\begin{itemize} 
> +\item Discovery and attachment of  virtio devices (as described above).

s/  / /

> +\item Initialization of virtqueues and transport specific facilities (using

s/transport specific/transport-specific/

Aside from that:

Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>

Attachment: signature.asc
Description: PGP signature