|
Should the TC accept changes listed in the description to resolve issue VIRTIO-158,
for inclusion in specification version(s) "virtio 1.1 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:
VIRTIO-158: ccw: clarify indicator requirements
--------------------------------------
The driver must set up its two-state indicators in a way that the device can set indicator bits for every queue it provides. This should be made more clear.
--------------------------------------
The TC accepts the following proposed changes to the specification:
--------------------------------------
Add an explicit statement that the driver needs to provide writeable indicators for all possible queues.
Proposed patch: https://www.oasis-open.org/apps/org/workgroup/virtio/email/archives/201702/msg00004.html
--------------------------------------
The TC agrees to include the above change(s) in specification version(s) "virtio 1.1 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.
--------------------------------------
|
