Commit 78d23416 authored by Donald Hunter's avatar Donald Hunter Committed by Jakub Kicinski

doc/netlink: Describe sub-message selector resolution

Update the netlink-raw docs to add a description of sub-message selector
resolution to explain that selector resolution is constrained by the
spec.
Signed-off-by: default avatarDonald Hunter <donald.hunter@gmail.com>
Reviewed-by: default avatarJiri Pirko <jiri@nvidia.com>
Link: https://lore.kernel.org/r/20240129223458.52046-4-donald.hunter@gmail.comSigned-off-by: default avatarJakub Kicinski <kuba@kernel.org>
parent bf8b8323
...@@ -150,3 +150,11 @@ attributes from an ``attribute-set``. For example the following ...@@ -150,3 +150,11 @@ attributes from an ``attribute-set``. For example the following
Note that a selector attribute must appear in a netlink message before any Note that a selector attribute must appear in a netlink message before any
sub-message attributes that depend on it. sub-message attributes that depend on it.
If an attribute such as ``kind`` is defined at more than one nest level, then a
sub-message selector will be resolved using the value 'closest' to the selector.
For example, if the same attribute name is defined in a nested ``attribute-set``
alongside a sub-message selector and also in a top level ``attribute-set``, then
the selector will be resolved using the value 'closest' to the selector. If the
value is not present in the message at the same level as defined in the spec
then this is an error.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment