From: Donald Hunter <donald.hunter@gmail.com>
To: netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>
Cc: donald.hunter@redhat.com, Donald Hunter <donald.hunter@gmail.com>
Subject: [PATCH net-next v1 0/3] netlink: add display-hint to ynl
Date: Fri, 23 Jun 2023 21:19:25 +0100 [thread overview]
Message-ID: <20230623201928.14275-1-donald.hunter@gmail.com> (raw)
Add a display-hint property to the netlink schema, to be used by generic
netlink clients as hints about how to display attribute values.
A display-hint on an attribute definition is intended for letting a
client such as ynl know that, for example, a u32 should be rendered as
an ipv4 address. The display-hint enumeration includes a small number of
networking domain-specific value types.
Donald Hunter (3):
netlink: specs: add display-hint to schema definitions
tools: ynl: add display-hint support to ynl
netlink: specs: add display hints to ovs_flow
Documentation/netlink/genetlink-c.yaml | 6 ++
Documentation/netlink/genetlink-legacy.yaml | 11 +-
Documentation/netlink/genetlink.yaml | 6 ++
Documentation/netlink/specs/ovs_flow.yaml | 107 ++++++++++++++++++++
tools/net/ynl/lib/nlspec.py | 10 ++
tools/net/ynl/lib/ynl.py | 34 ++++++-
6 files changed, 168 insertions(+), 6 deletions(-)
--
2.39.0
next reply other threads:[~2023-06-23 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 20:19 Donald Hunter [this message]
2023-06-23 20:19 ` [PATCH net-next v1 1/3] netlink: specs: add display-hint to schema definitions Donald Hunter
2023-06-23 20:19 ` [PATCH net-next v1 2/3] tools: ynl: add display-hint support to ynl Donald Hunter
2023-06-23 20:19 ` [PATCH net-next v1 3/3] netlink: specs: add display hints to ovs_flow Donald Hunter
2023-06-24 22:50 ` [PATCH net-next v1 0/3] netlink: add display-hint to ynl 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=20230623201928.14275-1-donald.hunter@gmail.com \
--to=donald.hunter@gmail.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@redhat.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--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).