[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [virtio-dev] Re: [PATCH 1/2] ccw: be more precise the semantic of revision 1
On Mon, Feb 12, 2018 at 03:25:12PM +0100, Halil Pasic wrote: > > > On 02/12/2018 01:59 PM, Cornelia Huck wrote: > > On Fri, 9 Feb 2018 20:59:13 +0100 > > Halil Pasic <pasic@linux.vnet.ibm.com> wrote: > > > > s/precise/precise about/ > > Nod. Should I spin a v2 or is it better handled > via fixup by maintainer? I prefer a respin. How about that jira issue(s)? You could then also include the # in the patch commit log then. Just say VIRTIO-XXXX in the commit log > > > >> Revision 1 of the CCW transport is currently defined as virtio 1.0. This > >> could become confusing when we bump the version of the virtio > >> specification to 1.1, in a sense that it could be interpreted like one > >> can not use any features not part of the 1.0 specification. > >> > >> So let us try to avoid confusion regarding the semantic of virtio-ccw > >> revision 1. > >> > >> Signed-off-by: Halil Pasic <pasic@linux.vnet.ibm.com> > >> --- > >> content.tex | 2 +- > >> 1 files changed, 1 insertions(+), 1 deletions(-) > >> > >> diff --git a/content.tex b/content.tex > >> index c7ef7fd..86044dd 100644 > >> --- a/content.tex > >> +++ b/content.tex > >> @@ -2572,7 +2572,7 @@ The following values are supported: > >> \hline \hline > >> 0 & 0 & <empty> & legacy interface; transitional devices only \\ > >> \hline > >> -1 & 0 & <empty> & Virtio 1.0 \\ > >> +1 & 0 & <empty> & Virtio 1 \\ > >> \hline > >> 2 & 0 & <empty> & CCW_CMD_READ_STATUS support \\ > >> \hline > > > > Reviewed-by: Cornelia Huck <cohuck@redhat.com> > > Thanks! > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org > > For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]