File 1010-man-describe-the-net-naming-schemes-specific-to-SLE.patch of Package systemd.26702

From 868659d1698c16c08703c807be8e6b01401a0ae5 Mon Sep 17 00:00:00 2001
From: Franck Bui <fbui@suse.com>
Date: Mon, 10 Oct 2022 16:31:39 +0200
Subject: [PATCH 1010/1010] man: describe the net naming schemes specific to
 SLE

Fixes: bsc#1204179
---
 man/systemd.net-naming-scheme.xml | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/man/systemd.net-naming-scheme.xml b/man/systemd.net-naming-scheme.xml
index ef3f262210..a50c3e4a31 100644
--- a/man/systemd.net-naming-scheme.xml
+++ b/man/systemd.net-naming-scheme.xml
@@ -390,6 +390,29 @@
     particular version of systemd).</para>
   </refsect1>
 
+  <refsect1>
+    <title>SLE History</title>
+
+    <para>Additionally, the following "naming schemes" have also been defined on SLE products:</para>
+
+    <variablelist>
+        <varlistentry>
+          <term><constant>sle15-sp3</constant></term>
+
+          <listitem><para>This naming scheme is available since <varname>SLE15-SP3</varname> and is based on
+          the <constant>v238</constant> naming scheme described previously but also includes the following
+          changes.</para>
+
+          <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>
+  </refsect1>
+
   <refsect1>
     <title>Examples</title>
 
-- 
2.35.3