public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Hangbin Liu <liuhangbin@gmail•com>
To: netdev@vger•kernel.org
Cc: Jakub Kicinski <kuba@kernel•org>, Paolo Abeni <pabeni@redhat•com>,
	Hangbin Liu <liuhangbin@gmail•com>
Subject: [PATCH net-next 3/3] netlink: specs: use exact-len for IPv6 addr
Date: Fri, 15 Dec 2023 11:50:09 +0800	[thread overview]
Message-ID: <20231215035009.498049-4-liuhangbin@gmail.com> (raw)
In-Reply-To: <20231215035009.498049-1-liuhangbin@gmail.com>

We should use the exact-len instead of min-len for IPv6 address.

Signed-off-by: Hangbin Liu <liuhangbin@gmail•com>
---
 Documentation/netlink/specs/fou.yaml   | 4 ++--
 Documentation/netlink/specs/mptcp.yaml | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/Documentation/netlink/specs/fou.yaml b/Documentation/netlink/specs/fou.yaml
index 0af5ab842c04..d472fd5055bd 100644
--- a/Documentation/netlink/specs/fou.yaml
+++ b/Documentation/netlink/specs/fou.yaml
@@ -52,7 +52,7 @@ attribute-sets:
         name: local_v6
         type: binary
         checks:
-          min-len: 16
+          exact-len: 16
       -
         name: peer_v4
         type: u32
@@ -60,7 +60,7 @@ attribute-sets:
         name: peer_v6
         type: binary
         checks:
-          min-len: 16
+          exact-len: 16
       -
         name: peer_port
         type: u16
diff --git a/Documentation/netlink/specs/mptcp.yaml b/Documentation/netlink/specs/mptcp.yaml
index 49f90cfb4698..2f694b79c3a7 100644
--- a/Documentation/netlink/specs/mptcp.yaml
+++ b/Documentation/netlink/specs/mptcp.yaml
@@ -223,7 +223,7 @@ attribute-sets:
         name: saddr6
         type: binary
         checks:
-          min-len: 16
+          exact-len: 16
       -
         name: daddr4
         type: u32
@@ -232,7 +232,7 @@ attribute-sets:
         name: daddr6
         type: binary
         checks:
-          min-len: 16
+          exact-len: 16
       -
         name: sport
         type: u16
-- 
2.43.0


  parent reply	other threads:[~2023-12-15  3:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-15  3:50 [PATCH net-next 0/3] ynl-gen: update check format Hangbin Liu
2023-12-15  3:50 ` [PATCH net-next 1/3] tools: ynl-gen: use correct len for string and binary Hangbin Liu
2023-12-16  2:06   ` Jakub Kicinski
2023-12-16  8:35     ` Hangbin Liu
2023-12-18 22:22       ` Jakub Kicinski
2023-12-19 10:01         ` Hangbin Liu
2023-12-15  3:50 ` [PATCH net-next 2/3] tools: ynl-gen: support using defines in checks Hangbin Liu
2023-12-16  2:08   ` Jakub Kicinski
2023-12-16  8:44     ` Hangbin Liu
2023-12-18 22:23       ` Jakub Kicinski
2023-12-15  3:50 ` Hangbin Liu [this message]
2023-12-16  2:09   ` [PATCH net-next 3/3] netlink: specs: use exact-len for IPv6 addr Jakub Kicinski
2023-12-16  8:48     ` Hangbin Liu
2023-12-18 22:24       ` Jakub Kicinski
2023-12-18 11:40   ` Davide Caratti

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=20231215035009.498049-4-liuhangbin@gmail.com \
    --to=liuhangbin@gmail$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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