Fix copy/paste bug in PCI transport paragraph
PATCH 1/1 Fix copy/paste bug in PCI transport paragraph
Refer to "Shared memory capability" and not to "Device-specific configuration".
--- content.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
content.tex +2 -2
@@ -1144,7 +1144,7 @@ \subsubsection{Shared memory capability}\label{sec:Virtio Transport Options / Vi The identifier in \field{cap.id} does not denote a certain order of preference; it is only used to uniquely identify a region. -\devicenormative{\paragraph}{Device-specific configuration}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Shared memory capability} +\devicenormative{\paragraph}{Shared memory capability}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Shared memory capability} The region defined by the combination of \field{cap.offset}, \field{offset_hi}, and \field {cap.length}, \field{length_hi}
@@ -1152,7 +1152,7 @@ \subsubsection{Shared memory capability}\label{sec:Virtio Transport Options / Vi The \field{cap.id} MUST be unique for any one device instance. -\devicenormative{\paragraph}{Device-specific configuration}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Shared memory capability} +\devicenormative{\paragraph}{Shared memory capability}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Shared memory capability} The region defined by the combination of the \field {cap.offset}, \field {cap.offset_hi}, and \field {cap.length}, \field
Signature · 18 lines
2.21.0 This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: [email protected] Unsubscribe: [email protected] List help: [email protected] List archive: https://lists.oasis-open.org/archives/virtio-comment/ Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists Committee: https://www.oasis-open.org/committees/virtio/ Join OASIS: https://www.oasis-open.org/join/
Quoted 22 lines · Max Gurtovoy
Refer to "Shared memory capability" and not to "Device-specific configuration".
Signed-off-by Max Gurtovoy <[email protected]>--- content.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)content.tex +1
-1@@ -1144,7 +1144,7 @@ \subsubsection{Shared memory capability}\label{sec:Virtio Transport Options / Vi The identifier in \field{cap.id} does not denote a certain order of preference; it is only used to uniquely identify a region. -\devicenormative{\paragraph}{Device-specific configuration}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Shared memory capability} +\devicenormative{\paragraph}{Shared memory capability}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Shared memory capability} The region defined by the combination of \field{cap.offset}, \field{offset_hi}, and \field {cap.length}, \field{length_hi}
content.tex \subsubsection{Shared memory capability}\label{sec:Virtio Transport Options / Vi · line 1158
Quoted 8 lines
content.tex +1
-1@@ -1152,7 +1152,7 @@ \subsubsection{Shared memory capability}\label{sec:Virtio Transport Options / Vi The \field{cap.id} MUST be unique for any one device instance. -\devicenormative{\paragraph}{Device-specific configuration}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Shared memory capability} +\devicenormative{\paragraph}{Shared memory capability}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Shared memory capability} The region defined by the combination of the \field {cap.offset}, \field {cap.offset_hi}, and \field {cap.length}, \field
And I guess we then need to fix the conformance clauses?
Quoted 2 lines
Signature · 1 line
2.21.0
Quoted 26 lines · Michael S. Tsirkin
Quoted 25 lines · Max Gurtovoy
Refer to "Shared memory capability" and not to "Device-specific configuration".
Signed-off-by Max Gurtovoy <[email protected]>--- content.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)content.tex +1
-1@@ -1144,7 +1144,7 @@ \subsubsection{Shared memory capability}\label{sec:Virtio Transport Options / Vi The identifier in \field{cap.id} does not denote a certain order of preference; it is only used to uniquely identify a region. -\devicenormative{\paragraph}{Device-specific configuration}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Shared memory capability} +\devicenormative{\paragraph}{Shared memory capability}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Shared memory capability} The region defined by the combination of \field{cap.offset}, \field{offset_hi}, and \field {cap.length}, \field{length_hi}@@ -1152,7 +1152,7 @@ \subsubsection{Shared memory capability}\label{sec:Virtio Transport Options / Vi The \field{cap.id} MUST be unique for any one device instance.
Quoted 7 lines
content.tex \subsubsection{Shared memory capability}\label{sec:Virtio Transport Options / Vi · line 1158
Quoted 5 lines
content.tex +1
-1-\devicenormative{\paragraph}{Device-specific configuration}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Shared memory capability} +\devicenormative{\paragraph}{Shared memory capability}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Shared memory capability} The region defined by the combination of the \field {cap.offset}, \field {cap.offset_hi}, and \field {cap.length}, \fieldAnd I guess we then need to fix the conformance clauses?
It looks ok actually there.
Quoted 3 lines
Quoted 3 lines
Signature · 2 lines
-- 2.21.0
Quoted 22 lines · Max Gurtovoy
Refer to "Shared memory capability" and not to "Device-specific configuration".
Signed-off-by Max Gurtovoy <[email protected]>--- content.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)content.tex +1
-1@@ -1144,7 +1144,7 @@ \subsubsection{Shared memory capability}\label{sec:Virtio Transport Options / Vi The identifier in \field{cap.id} does not denote a certain order of preference; it is only used to uniquely identify a region. -\devicenormative{\paragraph}{Device-specific configuration}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Shared memory capability} +\devicenormative{\paragraph}{Shared memory capability}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Shared memory capability} The region defined by the combination of \field{cap.offset}, \field{offset_hi}, and \field {cap.length}, \field{length_hi}
content.tex \subsubsection{Shared memory capability}\label{sec:Virtio Transport Options / Vi · line 1158
Quoted 8 lines
content.tex +1
-1@@ -1152,7 +1152,7 @@ \subsubsection{Shared memory capability}\label{sec:Virtio Transport Options / Vi The \field{cap.id} MUST be unique for any one device instance. -\devicenormative{\paragraph}{Device-specific configuration}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Shared memory capability} +\devicenormative{\paragraph}{Shared memory capability}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Shared memory capability} The region defined by the combination of the \field {cap.offset}, \field {cap.offset_hi}, and \field {cap.length}, \field
Thanks, pushed as an editorial update.
This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.
Subscribe: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/