From: Jakub Kicinski <kuba@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Mat Martineau <martineau@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Davide Caratti <dcaratti@redhat.com>
Subject: Re: [PATCH net-next 3/6] Documentation: netlink: add a YAML spec for mptcp
Date: Tue, 10 Oct 2023 18:08:39 -0700 [thread overview]
Message-ID: <20231010180839.0617d61d@kernel.org> (raw)
In-Reply-To: <20231010-upstream-net-next-20231006-mptcp-ynl-v1-3-18dd117e8f50@kernel.org>
On Tue, 10 Oct 2023 21:21:44 +0200 Matthieu Baerts wrote:
> +definitions:
> + -
> + type: enum
> + name: event-type
> + enum-name: mptcp_event_type
> + name-prefix: mptcp_event_
I think you can use - instead of _ here.
For consistency with other families?
> + entries:
> + -
> + name: unspec
> + value: 0
90% sure enums still start at 0, only attrs and msgs now default to 1.
> + -
> + name: announced
> + value: 6
> + doc:
> + token, rem_id, family, daddr4 | daddr6 [, dport]
> + A new address has been announced by the peer.
> + -
> + name: removed
> + value: 7
Follows 6 so no need for value?
> + doc:
> + token, rem_id
> + An address has been lost by the peer.
> + -
> + name: sub_established
Similarly for names we generally recommend - as a separator.
Looks more natural in places where it's used as a string, eg Python.
Well, I guess at least to me it does :)
> + value: 10
> + doc:
> + token, family, loc_id, rem_id, saddr4 | saddr6, daddr4 | daddr6, sport,
> + dport, backup, if_idx [, error]
> + A new subflow has been established. 'error' should not be set.
> + -
> + name: sub_closed
> + value: 11
and here, /value/d, s/_/-/
> + doc:
> + token, family, loc_id, rem_id, saddr4 | saddr6, daddr4 | daddr6, sport,
> + dport, backup, if_idx [, error]
> + A subflow has been closed. An error (copy of sk_err) could be set if an
> + error has been detected for this subflow.
> +attribute-sets:
> + -
> + name: address
> + name-prefix: mptcp_pm_addr_attr_
> + attributes:
> + -
> + name: unspec
> + type: unused
> + value: 0
> + -
> + name: family
> + type: u16
> + -
> + name: id
> + type: u8
> + -
> + name: addr4
> + type: u32
> + byte-order: big-endian
> + -
> + name: addr6
> + type: binary
> + checks:
> + min-len: 16
Do you not want the exact length for this?
If YNL doesn't support something just LMK, we add stuff as needed..
next prev parent reply other threads:[~2023-10-11 1:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 19:21 [PATCH net-next 0/6] mptcp: convert Netlink code to use YAML spec Matthieu Baerts
2023-10-10 19:21 ` [PATCH net-next 1/6] tools: ynl: add uns-admin-perm to genetlink legacy Matthieu Baerts
2023-10-10 19:21 ` [PATCH net-next 2/6] net: mptcp: convert netlink from small_ops to ops Matthieu Baerts
2023-10-10 19:21 ` [PATCH net-next 3/6] Documentation: netlink: add a YAML spec for mptcp Matthieu Baerts
2023-10-11 1:08 ` Jakub Kicinski [this message]
2023-10-11 10:13 ` Davide Caratti
2023-10-11 16:22 ` Jakub Kicinski
2023-10-10 19:21 ` [PATCH net-next 4/6] uapi: mptcp: use header file generated from YAML spec Matthieu Baerts
2023-10-13 17:28 ` Simon Horman
2023-10-14 11:37 ` Davide Caratti
2023-10-17 8:58 ` Simon Horman
2023-10-10 19:21 ` [PATCH net-next 5/6] net: mptcp: rename netlink handlers to mptcp_pm_nl_<blah>_{doit,dumpit} Matthieu Baerts
2023-10-10 19:21 ` [PATCH net-next 6/6] net: mptcp: use policy generated by YAML spec Matthieu Baerts
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=20231010180839.0617d61d@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).