From: Max Gurtovoy <mgurtovoy@nvidia.com>
To: virtio-comment@lists.oasis-open.org, mst@redhat.com, cohuck@redhat.com
Cc: oren@nvidia.com, stefanha@redhat.com, eperezma@redhat.com,
Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: [PATCH v2 1/1] Fix reserved Feature bits numbering
Date: Mon, 3 Jan 2022 19:03:44 +0200 [thread overview]
Message-ID: <20220103170344.3696-1-mgurtovoy@nvidia.com> (raw)
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>
---
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}
--
2.21.0
next reply other threads:[~2022-01-03 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 17:03 Max Gurtovoy [this message]
2022-01-03 17:20 ` [virtio-comment] Re: [PATCH v2 1/1] Fix reserved Feature bits numbering Cornelia Huck
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=20220103170344.3696-1-mgurtovoy@nvidia.com \
--to=mgurtovoy@nvidia.com \
--cc=cohuck@redhat.com \
--cc=eperezma@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox