Netdev List
 help / color / mirror / Atom feed
From: Minxi Hou <houminxi@gmail.com>
To: netdev@vger.kernel.org
Cc: donald.hunter@gmail.com, kuba@kernel.org, davem@davemloft.net,
	edumazet@google.com, pabeni@redhat.com, horms@kernel.org
Subject: [PATCH net-next v3 0/2] netlink: specs: fill in the missing ovs operations
Date: Wed, 14 Oct 2026 22:41:29 -0400	[thread overview]
Message-ID: <20261015024132.698658-1-houminxi@gmail.com> (raw)

The ovs specs describe get and new but not the set and del commands the
kernel has registered since the families were added. This series adds
them and names the attributes each handler reads. Nothing here changes
the kernel.

v3:
  - no change since v2 beyond the items listed above.

v2:
https://lore.kernel.org/netdev/20261012065552.2426415-1-houminxi@gmail.com/
  - ovs_flow new lists ufid-flags and probe, which ovs_flow_cmd_new()
    reads.
  - The commit message now says probe changes from binary to flag, and
    that new needs CAP_NET_ADMIN.
  - The key attribute doc no longer says a key is required for every
    request except a dump. get, set and del accept a ufid with no key,
    and only a new flow needs a key. A set that replaces the actions
    still needs a key.

v1:
https://lore.kernel.org/netdev/20261006130533.1620706-1-houminxi@gmail.com/
  - probe is a flag, matching the NLA_FLAG policy. A false flag is left
    out, where the binary attribute was sent empty.
  - del lists probe.
  - The set doc says replacing the actions needs a key even when a ufid
    is present.

Minxi Hou (2):
  netlink: specs: add ovs_flow del and set operations
  netlink: specs: add ovs datapath and vport set operations

 Documentation/netlink/specs/ovs_datapath.yaml | 18 +++++++
 Documentation/netlink/specs/ovs_flow.yaml     | 41 ++++++++++++++++++-
 Documentation/netlink/specs/ovs_vport.yaml    | 15 +++++++
 3 files changed, 72 insertions(+), 2 deletions(-)

Signed-off-by: Minxi Hou <houminxi@gmail.com>

base-commit: 05b5019b01fb9443b09ae4ed34af1135a80a84c8
-- 
2.56.0

             reply	other threads:[~2026-10-15  2:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15  2:41 Minxi Hou [this message]
2026-10-15  2:41 ` [PATCH net-next v3 1/2] netlink: specs: add ovs_flow del and set operations Minxi Hou
2026-10-15  2:41 ` [PATCH net-next v3 2/2] netlink: specs: add ovs datapath and vport " Minxi Hou

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=20261015024132.698658-1-houminxi@gmail.com \
    --to=houminxi@gmail.com \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --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