From: Cornelia Huck <cohuck@redhat.com>
To: Max Gurtovoy <mgurtovoy@nvidia.com>,
mst@redhat.com, virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org
Cc: oren@nvidia.com, Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: [virtio-comment] Re: [PATCH 1/1] virtio-blk: fix virtqueues accounting
Date: Thu, 22 Jul 2021 12:20:49 +0200 [thread overview]
Message-ID: <87sg067ipq.fsf@redhat.com> (raw)
In-Reply-To: <20210721124530.37225-1-mgurtovoy@nvidia.com>
On Wed, Jul 21 2021, Max Gurtovoy <mgurtovoy@nvidia.com> wrote:
> Virtqueue index is zero based, thus virtqueue (N-1) refers to requestqN.
>
> Signed-off-by: Max Gurtovoy <mgurtovoy@nvidia.com>
> ---
> content.tex | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
We had an issue for a similar fix for virtio-net, so do we want to use
issue+voting here as well, or would that be overkill? I'm inclined to do
this as an editorial update.
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:[~2021-07-22 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 12:45 [PATCH 1/1] virtio-blk: fix virtqueues accounting Max Gurtovoy
2021-07-22 10:20 ` Cornelia Huck [this message]
2021-08-10 6:39 ` [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=87sg067ipq.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=mgurtovoy@nvidia.com \
--cc=mst@redhat.com \
--cc=oren@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@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