From: Cornelia Huck <cohuck@redhat.com>
To: Max Gurtovoy <mgurtovoy@nvidia.com>,
virtio-comment@lists.oasis-open.org, mst@redhat.com
Cc: oren@nvidia.com, stefanha@redhat.com, eperezma@redhat.com,
Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: [virtio-comment] Re: [PATCH v2 1/1] Fix reserved Feature bits numbering
Date: Mon, 03 Jan 2022 18:20:45 +0100 [thread overview]
Message-ID: <87mtkcwxaq.fsf@redhat.com> (raw)
In-Reply-To: <20220103170344.3696-1-mgurtovoy@nvidia.com>
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?
> ---
>
> 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.
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2022-01-03 17:20 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 ` Cornelia Huck [this message]
2022-01-03 17:42 ` Max Gurtovoy
2022-01-03 21:48 ` Michael S. Tsirkin
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=87mtkcwxaq.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=eperezma@redhat.com \
--cc=mgurtovoy@nvidia.com \
--cc=mst@redhat.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.