OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

virtio message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (VIRTIO-72) SHOULD/should


     [ https://tools.oasis-open.org/issues/browse/VIRTIO-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Tsirkin updated VIRTIO-72:
----------------------------------

    Resolution: 

accepted on 2014-03-11
applied in commit r321

> SHOULD/should
> -------------
>
>                 Key: VIRTIO-72
>                 URL: https://tools.oasis-open.org/issues/browse/VIRTIO-72
>             Project: OASIS Virtual I/O Device (VIRTIO) TC
>          Issue Type: Bug
>         Environment: Keywords
>            Reporter: Patrick Durusau
>
> SHOULD appears 12 times and should appears 67 times.
> Some of the lower case uses of "should" appear to be in non-normative text that should be notes. But in other cases, it appears to be the equivalent of "SHOULD."
> From 3.1 Device Initialization:
> *****
> the driver SHOULD set the FAILED status bit to indicate that it has given up on the device (it can reset the device later to restart if desired).
> *****
> From 3.2.2 Receiving Used Buffers from the Device
> *****
> For each ring, the driver should then disable interrupts by writing VRING_AVAIL_F_NO_INTERRUPT flag in avail structure, if required. 
> *****
> The "shoulds" in those two cases have very different meaning for conforming to VIRTIO.
> The first is RFC2119 "SHOULD" and the second is just ordinary should, really non-normative.



--
This message was sent by Atlassian JIRA
(v6.1.1#6155)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]