From: Donald Hunter <donald.hunter@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Andrew Lunn <andrew@lunn.ch>,
"Matthieu Baerts (NGI0)" <matttbe@kernel.org>,
Chuck Lever <chuck.lever@oracle.com>,
Florian Westphal <fw@strlen.de>,
"Remy D. Farley" <one-d-wide@protonmail.com>,
"Kory Maincent (Dent Project)" <kory.maincent@bootlin.com>,
Gal Pressman <gal@nvidia.com>,
Oleksij Rempel <o.rempel@pengutronix.de>,
Stanislav Fomichev <sdf@fomichev.me>,
Jan Stancek <jstancek@redhat.com>,
Hangbin Liu <liuhangbin@gmail.com>,
Nimrod Oren <noren@nvidia.com>,
netdev@vger.kernel.org
Cc: Donald Hunter <donald.hunter@gmail.com>
Subject: [PATCH net-next v1 4/4] ynl: fix schema check errors
Date: Thu, 27 Nov 2025 12:35:02 +0000 [thread overview]
Message-ID: <20251127123502.89142-5-donald.hunter@gmail.com> (raw)
In-Reply-To: <20251127123502.89142-1-donald.hunter@gmail.com>
Fix two schema check errors that have lurked since the attribute name
validation was made more strict:
not ok 2 conntrack.yaml schema validation
'labels mask' does not match '^[0-9a-z-]+$'
not ok 13 nftables.yaml schema validation
'set id' does not match '^[0-9a-z-]+$'
Signed-off-by: Donald Hunter <donald.hunter@gmail.com>
---
Documentation/netlink/specs/conntrack.yaml | 2 +-
Documentation/netlink/specs/nftables.yaml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/netlink/specs/conntrack.yaml b/Documentation/netlink/specs/conntrack.yaml
index bef528633b17..db7cddcda50a 100644
--- a/Documentation/netlink/specs/conntrack.yaml
+++ b/Documentation/netlink/specs/conntrack.yaml
@@ -457,7 +457,7 @@ attribute-sets:
name: labels
type: binary
-
- name: labels mask
+ name: labels-mask
type: binary
-
name: synproxy
diff --git a/Documentation/netlink/specs/nftables.yaml b/Documentation/netlink/specs/nftables.yaml
index cce88819ba71..17ad707fa0d5 100644
--- a/Documentation/netlink/specs/nftables.yaml
+++ b/Documentation/netlink/specs/nftables.yaml
@@ -915,7 +915,7 @@ attribute-sets:
type: string
doc: Name of set to use
-
- name: set id
+ name: set-id
type: u32
byte-order: big-endian
doc: ID of set to use
--
2.51.1
next prev parent reply other threads:[~2025-11-27 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 12:34 [PATCH net-next v1 0/4] tools: ynl: add schema checking Donald Hunter
2025-11-27 12:34 ` [PATCH net-next v1 1/4] " Donald Hunter
2025-11-27 12:35 ` [PATCH net-next v1 2/4] tools: ynl: add a lint makefile target Donald Hunter
2025-11-27 12:35 ` [PATCH net-next v1 3/4] ynl: fix a yamllint warning in ethtool spec Donald Hunter
2025-11-27 12:35 ` Donald Hunter [this message]
2025-11-29 4:00 ` [PATCH net-next v1 0/4] tools: ynl: add schema checking patchwork-bot+netdevbpf
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=20251127123502.89142-5-donald.hunter@gmail.com \
--to=donald.hunter@gmail.com \
--cc=andrew@lunn.ch \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=jstancek@redhat.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=matttbe@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noren@nvidia.com \
--cc=o.rempel@pengutronix.de \
--cc=one-d-wide@protonmail.com \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
/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;
as well as URLs for NNTP newsgroup(s).