From: Jonathon Jongsma <jjongsma@redhat.com>
Date: Thu, 21 May 2020 20:09:34 +0000 (-0500)
Subject: docs: Fix names for PF and VF PCI device capabilities
X-Git-Tag: v6.4.0-rc1~26
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e68c290f4b2277c93a9fea422bd261429751ed4c;p=thirdparty%2Flibvirt.git

docs: Fix names for PF and VF PCI device capabilities

The proper name for physical function capability is 'phys_function', not
'physical_function'. Likewise, a virtual function capability is
'virt_functions' rather than 'virtual_function'.

Signed-off-by: Jonathon Jongsma <jjongsma@redhat.com>
Reviewed-by: Erik Skultety <eskultet@redhat.com>
---

diff --git a/docs/formatnode.html.in b/docs/formatnode.html.in
index c2a8f8fb7a..7dcd3638ff 100644
--- a/docs/formatnode.html.in
+++ b/docs/formatnode.html.in
@@ -109,7 +109,7 @@
                 exists, it has a mandatory <code>type</code> attribute
                 which will be set to:
                 <dl>
-                  <dt><code>physical_function</code></dt>
+                  <dt><code>phys_function</code></dt>
                   <dd>
                     That means there will be a single <code>address</code>
                     subelement which contains the PCI address of the SRIOV
@@ -117,7 +117,7 @@
                     (and this device is, by implication, an SRIOV Virtual
                     Function (VF)).
                   </dd>
-                  <dt><code>virtual_function</code></dt>
+                  <dt><code>virt_functions</code></dt>
                   <dd>
                     In this case this device is an SRIOV PF, and the capability
                     element will have a list of <code>address</code>