summaryrefslogtreecommitdiffstats
path: root/man/systemd.net-naming-scheme.xml
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2021-01-28 20:38:27 +0100
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2021-01-29 08:42:39 +0100
commit75909cc7e48d6ebfa7c61bee1b089dd4e1ba0b5f (patch)
tree42ae0163d920fcb2ef13529308775ace67a8ff6f /man/systemd.net-naming-scheme.xml
parentman: rework description of --timestamp (diff)
downloadsystemd-75909cc7e48d6ebfa7c61bee1b089dd4e1ba0b5f.tar.xz
systemd-75909cc7e48d6ebfa7c61bee1b089dd4e1ba0b5f.zip
man: various typos and other small issues
Fixes #18397.
Diffstat (limited to 'man/systemd.net-naming-scheme.xml')
-rw-r--r--man/systemd.net-naming-scheme.xml12
1 files changed, 6 insertions, 6 deletions
diff --git a/man/systemd.net-naming-scheme.xml b/man/systemd.net-naming-scheme.xml
index 054de92c0b..646dd3e561 100644
--- a/man/systemd.net-naming-scheme.xml
+++ b/man/systemd.net-naming-scheme.xml
@@ -271,7 +271,7 @@
<title>History</title>
<para>The following "naming schemes" have been defined (which may be chosen at system boot-up time via
- the <varname>net.naming-scheme=</varname> kernel command line switch, see above:</para>
+ the <varname>net.naming-scheme=</varname> kernel command line switch, see above):</para>
<variablelist>
<varlistentry>
@@ -362,11 +362,11 @@
<varlistentry>
<term><constant>v247</constant></term>
- <listitem><para>If the PCI slot is associated with PCI bridge and that has multiple child network
- controllers then all of them might derive the same value of <varname>ID_NET_NAME_SLOT</varname>
- property. That could cause naming conflict if the property is selected as a device name. Now, we detect the
- situation, slot - bridge relation, and we don't produce the <varname>ID_NET_NAME_SLOT</varname> property to
- avoid possible naming conflict.</para></listitem>
+ <listitem><para>When a PCI slot is associated with a PCI bridge that has multiple child network
+ controllers, the same value of the <varname>ID_NET_NAME_SLOT</varname> property might be derived
+ for those controllers. This would cause a naming conflict if the property is selected as the device
+ name. Now, we detect this situation and don't produce the <varname>ID_NET_NAME_SLOT</varname>
+ property.</para></listitem>
</varlistentry>
</variablelist>