From: Minxi Hou <houminxi@gmail.com>
To: netdev@vger.kernel.org
Cc: donald.hunter@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, aconole@redhat.com,
linux-kernel@vger.kernel.org, Minxi Hou <houminxi@gmail.com>
Subject: [PATCH net-next v3 0/2] Add OVS packet family YNL spec and unicast notification support
Date: Tue, 19 May 2026 18:31:51 +0800 [thread overview]
Message-ID: <20260519103153.968549-1-houminxi@gmail.com> (raw)
This series adds a YAML netlink spec for the OVS_PACKET_FAMILY genetlink
family and a bind-only ntf_listen() helper for receiving unicast
notifications.
Changes in v3:
- patch 1: add missing document start "---" after SPDX comment
(yamllint warning in v2)
Changes in v2:
- patch 1: use YAML anchor (&event-attrs / *event-attrs) to avoid
repeating the same attribute list for miss and action events
(suggested by Donald Hunter)
- patch 1: fix enum-name from ovs-packet-attrs to ovs-packet-attr
to match the kernel enum name ovs_packet_attr
- patch 2: add ntf_listen() to the YnlFamily docstring under the
"Notification API" heading (suggested by Donald Hunter)
Minxi Hou (2):
netlink: specs: add OVS packet family specification
tools: ynl: add unicast notification receive support
Documentation/netlink/specs/ovs_packet.yaml | 130 ++++++++++++++++++++
tools/net/ynl/pyynl/lib/ynl.py | 5 +
2 files changed, 135 insertions(+)
create mode 100644 Documentation/netlink/specs/ovs_packet.yaml
--
2.54.0
next reply other threads:[~2026-05-19 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 10:31 Minxi Hou [this message]
2026-05-19 10:31 ` [PATCH net-next v3 1/2] netlink: specs: add OVS packet family specification Minxi Hou
2026-05-19 10:31 ` [PATCH net-next v3 2/2] tools: ynl: add unicast notification receive support Minxi Hou
2026-05-19 11:26 ` [PATCH net-next v3 0/2] Add OVS packet family YNL spec and unicast notification support 侯敏熙
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=20260519103153.968549-1-houminxi@gmail.com \
--to=houminxi@gmail.com \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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