|
Should the TC accept changes listed in the description to resolve issue 168,
for inclusion in specification version(s) "virtio-v1.3-cs01", and future versions of the specification?
Please vote Yes if you agree with all of the following.
If you disagree, please vote No.
If you don't have an opinion, please vote Abstain.
I move that:
The TC agrees to resolve the following specification issue:
Issue #168: Correct virtual queue to virtqueue for MMIO transport
--------------------------------------
Problem: MMIO device refers to the virtqueue as "virtual queue".
virtio specification all over refers to this as virtqueue object.
Solution: Correct it to refer to it as virtqueue.
Patch for vote: https://lists.oasis-open.org/archives/virtio-comment/202305/msg00185.html
Patch for maintainer automation: https://lore.kernel.org/virtio-comment/20230511163020.708427-1-parav@nvidia.com/T/#u
--------------------------------------
The TC accepts the following proposed changes to the specification:
--------------------------------------
https://lists.oasis-open.org/archives/virtio-comment/202305/msg00185.html
--------------------------------------
The TC agrees to include the above change(s) in specification version(s) "virtio-v1.3-cs01", and future versions of the
specification.
--------------------------------------
Reminder: A Voting Member must be active in a TC to maintain voting rights. As
the Virtio TC has adopted a standing rule to conduct business only by
electronic ballot, without Meetings, a Voting Member who fails to cast a ballot
in two consecutive Work Product Ballots loses his or her voting rights at the
close of the second ballot missed.
--------------------------------------
|
