]> git.ipfire.org Git - thirdparty/kernel/linux.git/commit
netlink: specs: explicitly declare block scalar strings
authorMatthieu Baerts (NGI0) <matttbe@kernel.org>
Sat, 13 Sep 2025 13:29:53 +0000 (15:29 +0200)
committerJakub Kicinski <kuba@kernel.org>
Tue, 16 Sep 2025 01:27:19 +0000 (18:27 -0700)
commit12e74931ee9792b5256f4433efd779cfd0aca443
treea4ae510f085f6a22de851f9cbe9fb55b752324da
parent515c0ead788f4118a91b3ae55fe51f95543553ec
netlink: specs: explicitly declare block scalar strings

In YAML, it is allowed to declare a scalar strings at the next lines
without explicitly declaring them as a block. Yet, they looks weird, and
can cause issues when ':' or '#' are present.

The modified lines didn't have issues with the special characters, but
it seems better to explicitly declare such blocks as scalar strings to
encourage people to "properly" declare future scalar strings.

The right angle bracket is used with a minus sign to indicate that the
folded style should be used without adding extra newlines. By doing
that, the output is not changed compared to what was done before this
patch.

Suggested-by: Donald Hunter <donald.hunter@gmail.com>
Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Link: https://patch.msgid.link/20250913-net-next-ynl-attr-doc-rst-v3-3-4f06420d87db@kernel.org
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
13 files changed:
Documentation/netlink/specs/conntrack.yaml
Documentation/netlink/specs/netdev.yaml
Documentation/netlink/specs/nftables.yaml
Documentation/netlink/specs/nl80211.yaml
Documentation/netlink/specs/ovs_datapath.yaml
Documentation/netlink/specs/ovs_flow.yaml
Documentation/netlink/specs/ovs_vport.yaml
Documentation/netlink/specs/rt-addr.yaml
Documentation/netlink/specs/rt-link.yaml
Documentation/netlink/specs/rt-neigh.yaml
Documentation/netlink/specs/rt-route.yaml
Documentation/netlink/specs/rt-rule.yaml
Documentation/netlink/specs/tc.yaml