From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Max Gurtovoy <mgurtovoy@nvidia.com>,
virtio-comment@lists.oasis-open.org, oren@nvidia.com,
stefanha@redhat.com, eperezma@redhat.com
Subject: Re: [PATCH v2 1/1] Fix reserved Feature bits numbering
Date: Mon, 3 Jan 2022 16:48:48 -0500 [thread overview]
Message-ID: <20220103164709-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <87mtkcwxaq.fsf@redhat.com>
On Mon, Jan 03, 2022 at 06:20:45PM +0100, Cornelia Huck wrote:
> On Mon, Jan 03 2022, Max Gurtovoy <mgurtovoy@nvidia.com> wrote:
>
> > This should have been updated during VIRTIO_F_NOTIFICATION_DATA,
> > VIRTIO_F_NOTIF_CONFIG_DATA and VIRTIO_F_RING_RESET standartization.
> >
> > Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> > Signed-off-by: Max Gurtovoy <mgurtovoy@nvidia.com>
>
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/128
>
> Can you please also update the archive link in the issue, once the mail
> shows up there?
Wish we had a cleaner way to do it than updating this each time we
add a generic feature bit.
> > ---
> >
> > changes from v1:
> > - added "Reviewed-by" signature (Stefan)
> > - include VIRTIO_F_RING_RESET feature bit (Cornelia)
> >
> > ---
> > content.tex | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/content.tex b/content.tex
> > index cf20570..32de668 100644
> > --- a/content.tex
> > +++ b/content.tex
> > @@ -99,10 +99,10 @@ \section{Feature Bits}\label{sec:Basic Facilities of a Virtio Device / Feature B
> > \begin{description}
> > \item[0 to 23] Feature bits for the specific device type
> >
> > -\item[24 to 37] Feature bits reserved for extensions to the queue and
> > +\item[24 to 40] Feature bits reserved for extensions to the queue and
> > feature negotiation mechanisms
> >
> > -\item[38 and above] Feature bits reserved for future extensions.
> > +\item[41 and above] Feature bits reserved for future extensions.
> > \end{description}
> >
> > \begin{note}
>
> LGTM.
next prev parent reply other threads:[~2022-01-03 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 17:03 [PATCH v2 1/1] Fix reserved Feature bits numbering Max Gurtovoy
2022-01-03 17:20 ` [virtio-comment] " Cornelia Huck
2022-01-03 17:42 ` Max Gurtovoy
2022-01-03 21:48 ` Michael S. Tsirkin [this message]
2022-01-04 8:10 ` [virtio-comment] " 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=20220103164709-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=eperezma@redhat.com \
--cc=mgurtovoy@nvidia.com \
--cc=oren@nvidia.com \
--cc=stefanha@redhat.com \
--cc=virtio-comment@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.