Ballot Details: Resolve Issue #110: Add virtio-gpio base specification (CLOSED) |
|||||||||
Ballot Question | Should the TC accept changes listed in the description to resolve issue 110, for inclusion in specification version(s) "virtio-v1.2-cs01", and future versions of the specification? | ||||||||
Ballot Description | 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 #110: Add virtio-gpio base specification -------------------------------------- https://lists.oasis-open.org/archives/virtio-dev/202108/msg00058.html -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-dev/202108/msg00058.html -------------------------------------- The TC agrees to include the above change(s) in specification version(s) "virtio-v1.2-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. -------------------------------------- |
||||||||
Ballot Options |
VOTING CLOSED: Tuesday, 17 August 2021 @ 6:15 am EDT
|
||||||||
Open Date | Tuesday, 10 August 2021 @ 6:15 am EDT | ||||||||
Close Date | Tuesday, 17 August 2021 @ 6:15 am EDT | ||||||||
Ballot Type | Official, as defined by organization policies and procedures |
Number of votes cast (excluding abstentions) | 8 | |
Eligible members who have voted | 8 of 8 | 100% |
Eligible members who have not voted | 0 of 8 | 0% |
Options with highest number of votes are bold | ||
Option | # Votes | % of Total |
---|---|---|
Yes | 8 | 100% |
No | 0 | 0% |
Abstain | 0 |
Voter Name | Company |
Vote
![]() |
Time (UTC) | Comments |
---|---|---|---|---|
![]() |
Oracle | Yes | 2021-08-12 11:47:00 | |
![]() |
Google Inc. | Yes | 2021-08-10 16:57:00 | |
![]() |
Red Hat | Yes | 2021-08-16 17:02:00 | 1 |
![]() |
Red Hat | Yes | 2021-08-10 10:46:00 | |
![]() |
Siemens AG | Yes | 2021-08-17 08:02:00 | |
![]() |
OpenSynergy GmbH | Yes | 2021-08-10 16:29:00 | |
![]() |
IBM | Yes | 2021-08-13 15:03:00 | |
![]() |
Red Hat | Yes | 2021-08-13 19:59:00 |
Submitter | Vote ![]() |
Comment |
---|---|---|
Hajnoczi, Stefan Red Hat |
Yes | Overall this looks fine, but I'd like to request a follow-up specifying the character encoding of VIRTIO_GPIO_MSG_GET_LINE_NAMES. The spec does not make it clear whether ASCII or UTF-8 or another encoding is used. |