NEWS, man: move description of SR-IOV-R net naming to v255
https://github.com/systemd/systemd/pull/29582 adds the "v254" name. This also changes what the default is and what "latest" refers to. Without the name, the code could be enabled via runtime configuration. Nevertheless, it could be enabled at compilation time. In other words: meson setup build -Ddefault-net-naming-scheme=v254 would work, but net.naming-scheme=v254 would fail. It is possible that people were using the compile-time override, so I think we should allow "v254" scheme to stay and clearly document that it wasn't the default. Unfortunately, unless people manually introduced the compile-time override, we were never actually testing the new code too. So all the pull request testing was not useful.
This commit is contained in:
@@ -27,6 +27,7 @@ static const NamingScheme naming_schemes[] = {
|
||||
{ "v252", NAMING_V252 },
|
||||
{ "v253", NAMING_V253 },
|
||||
{ "v254", NAMING_V254 },
|
||||
{ "v255", NAMING_V255 },
|
||||
/* … add more schemes here, as the logic to name devices is updated … */
|
||||
|
||||
EXTRA_NET_NAMING_MAP
|
||||
|
||||
@@ -54,7 +54,11 @@ typedef enum NamingSchemeFlags {
|
||||
NAMING_V251 = NAMING_V250 | NAMING_BRIDGE_MULTIFUNCTION_SLOT,
|
||||
NAMING_V252 = NAMING_V251 | NAMING_DEVICETREE_ALIASES,
|
||||
NAMING_V253 = NAMING_V252 | NAMING_USB_HOST,
|
||||
NAMING_V254 = NAMING_V253 | NAMING_SR_IOV_R,
|
||||
NAMING_V254 = NAMING_V253 | NAMING_SR_IOV_R, /* Despite the name, "v254" is NOT the default scheme
|
||||
* for systemd version 254. It was added in a follow-up
|
||||
* patch later. NAMING_SR_IOV_R is enabled by default in
|
||||
* systemd version 255, naming scheme "v255". */
|
||||
NAMING_V255 = NAMING_V254,
|
||||
|
||||
EXTRA_NET_NAMING_SCHEMES
|
||||
|
||||
|
||||
Reference in New Issue
Block a user