summaryrefslogtreecommitdiffstats
path: root/man/systemd.net-naming-scheme.xml
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--man/systemd.net-naming-scheme.xml6
1 files changed, 5 insertions, 1 deletions
diff --git a/man/systemd.net-naming-scheme.xml b/man/systemd.net-naming-scheme.xml
index 0dd8728c25..bb78990145 100644
--- a/man/systemd.net-naming-scheme.xml
+++ b/man/systemd.net-naming-scheme.xml
@@ -478,7 +478,8 @@
bridge as that would create naming conflict when there are more child devices on that bridge. Now,
this is relaxed and we will use slot information to generate the name based on it but only if
the PCI device has multiple functions. This is safe because distinct function number is a part of
- the device name for multifunction devices.</para>
+ the device name for multifunction devices. Note, this is reverted in <constant>v255</constant>.
+ See below.</para>
<xi:include href="version-info.xml" xpointer="v251"/>
</listitem>
@@ -521,6 +522,9 @@
<listitem><para>Naming was changed for SR-IOV virtual device representors to enable the
change introduced in <constant>v254</constant> by default.</para>
+ <para>If we detect that a PCI device associated with a slot is a PCI bridge, we no longer set
+ <varname>ID_NET_NAME_SLOT</varname>, reverting a change that was introduced in v251.</para>
+
<xi:include href="version-info.xml" xpointer="v255"/>
</listitem>
</varlistentry>