From: "Asbjørn Sloth Tønnesen" <ast@fiberby.net>
To: netdev@vger.kernel.org
Cc: "Asbjørn Sloth Tønnesen" <ast@fiberby.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Donald Hunter" <donald.hunter@gmail.com>,
"Danielle Ratson" <danieller@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Greg Thelen" <gthelen@google.com>,
"Ilya Maximets" <i.maximets@ovn.org>,
"Matthieu Baerts (Netdev Foundation)" <matttbe@kernel.org>,
"Maxime Chevallier (Netdev Foundation)"
<maxime.chevallier@bootlin.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Remy D. Farley" <one-d-wide@protonmail.com>,
"Simon Horman" <horms@kernel.org>,
"Stanislav Fomichev" <sdf.kernel@gmail.com>,
"Heng Guo" <heng.guo@windriver.com>,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH net-next 8/8] netlink: specs: rt-link: fix netkit-policy names
Date: Thu, 10 Sep 2026 22:17:28 +0000 [thread overview]
Message-ID: <20260910221733.1021864-9-ast@fiberby.net> (raw)
In-Reply-To: <20260910221733.1021864-1-ast@fiberby.net>
Correct the names of these `enum netkit_action` constants:
- NETKIT_PASS is 0, so "pass", not "forward".
- NETKIT_DROP is 2, so "drop", not "blackhole".
Note, the other enum members are not used in netlink, and
are not allowed by netkit_check_policy().
Signed-off-by: Asbjørn Sloth Tønnesen <ast@fiberby.net>
---
Documentation/netlink/specs/rt-link.yaml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/netlink/specs/rt-link.yaml b/Documentation/netlink/specs/rt-link.yaml
index 6639b7f5677b..fe52d508d607 100644
--- a/Documentation/netlink/specs/rt-link.yaml
+++ b/Documentation/netlink/specs/rt-link.yaml
@@ -827,10 +827,10 @@ definitions:
name-prefix: netkit-
entries:
-
- name: forward
+ name: pass
value: 0
-
- name: blackhole
+ name: drop
value: 2
-
name: netkit-mode
--
2.55.0
prev parent reply other threads:[~2026-09-10 22:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 22:17 [RFC PATCH net-next 0/8] tools: ynl: C-based YNL linter Asbjørn Sloth Tønnesen
2026-09-10 22:17 ` [RFC PATCH net-next 1/8] netlink: specs: nftables: add uapi-header Asbjørn Sloth Tønnesen
2026-09-10 22:17 ` [RFC PATCH net-next 2/8] netlink: specs: conntrack: " Asbjørn Sloth Tønnesen
2026-09-11 2:35 ` Jakub Kicinski
2026-09-10 22:17 ` [RFC PATCH net-next 3/8] tools: ynl: add C-based YNL linter Asbjørn Sloth Tønnesen
2026-09-11 2:33 ` Jakub Kicinski
2026-09-11 22:27 ` Asbjørn Sloth Tønnesen
2026-09-10 22:17 ` [RFC PATCH net-next 4/8] netlink: specs: rt-link: add C naming info Asbjørn Sloth Tønnesen
2026-09-10 22:17 ` [RFC PATCH net-next 5/8] netlink: specs: rt-link: re-align IPv4 devconf Asbjørn Sloth Tønnesen
2026-09-10 22:17 ` [RFC PATCH net-next 6/8] netlink: specs: rt-link: re-align ifla-inet6-stats Asbjørn Sloth Tønnesen
2026-09-10 22:17 ` [RFC PATCH net-next 7/8] netlink: specs: rt-link: fix ifinfo-flags names Asbjørn Sloth Tønnesen
2026-09-10 22:17 ` Asbjørn Sloth Tønnesen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260910221733.1021864-9-ast@fiberby.net \
--to=ast@fiberby.net \
--cc=danieller@nvidia.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=gthelen@google.com \
--cc=heng.guo@windriver.com \
--cc=horms@kernel.org \
--cc=i.maximets@ovn.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=one-d-wide@protonmail.com \
--cc=pabeni@redhat.com \
--cc=sdf.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox