virtio — archive

[PATCH 00/18] Feedback: conformance clauses and normative statements.

From: Rusty Russell <[email protected]>
To: [email protected]
Date: Wed, 19 Feb 2014 06:45:00 -0000

From http://docs.oasis-open.org/templates/TCHandbook/ConformanceGuidelines.html: Normative statements MUST be referenceable so that a statement may be referenced from another part of a specification, but more importantly so they can be referenced from Conformance Clauses. Signed-off-by: Rusty Russell <[email protected]> --- commands.tex 4 ++++ content.tex 2 ++ 2 files changed, 6 insertions(+) diff --git a/commands.tex b/commands.tex index 671757b..c4b19de 100644 --- a/commands.tex +++ b/commands.tex @@ -8,3 +8,7 @@ % How we format a field name ewcommand{field}[1]{emph{#1}} + +% Mark a normative paragraph (driver or device) + ewcommand{drivernormative}[1]{phantomsectionlabel{drivernormative:#1}} + ewcommand{devicenormative}[1]{phantomsectionlabel{devicenormative:#1}} diff --git a/content.tex b/content.tex index 88c6d6a..dd9b8a7 100644 --- a/content.tex +++ b/content.tex @@ -40,11 +40,13 @@ following bits are defined: even a fatal error during device operation. end{description} +drivernormative{Basic Facilities of a Virtio Device / Device Status Field} The driver MUST update field{device status} in the order above to indicate the driver's progress. The driver MUST NOT clear a field{device status} bit. If the driver sets the FAILED bit, it MUST reset the device before attempting to re-initialize. +devicenormative{Basic Facilities of a Virtio Device / Device Status Field} The device MUST initialize field{device status} to 0 upon reset. section{Feature Bits}label{sec:Basic Facilities of a Virtio Device / Feature Bits} -- 1.8.3.2