From: patchwork-bot+netdevbpf@kernel.org
To: Minxi Hou <houminxi@gmail.com>
Cc: netdev@vger.kernel.org, dev@openvswitch.org, aconole@redhat.com,
davem@davemloft.net, donald.hunter@gmail.com,
echaudro@redhat.com, edumazet@kernel.org, i.maximets@ovn.org,
kuba@kernel.org, linux-kernel@vger.kernel.org, pabeni@redhat.com,
horms@kernel.org
Subject: Re: [PATCH net-next v9 0/3] netlink: specs: fill in the missing ovs operations
Date: Sat, 21 Nov 2026 23:50:06 +0000 [thread overview]
Message-ID: <179530500653.1221130.3267976128355385798.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261119172118.3416958-1-houminxi@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 19 Nov 2026 12:21:15 -0500 you wrote:
> The ovs specs describe get and new but not every command the kernel
> has registered: all three families lacked set, and ovs_flow also lacked
> del. This series adds them, names the attributes each handler reads,
> and corrects what the existing specs say about the kernel. No kernel
> code changes.
>
> v9:
> https://lore.kernel.org/netdev/20261115072638.3163018-1-houminxi@gmail.com/
> - Rebased onto current net-next.
> - The note on the vport name is a complete sentence again. The v8
> wording stopped after "dp_ifindex from", so the sentence that says
> what the lookup falls back to was missing.
> v8:
> https://lore.kernel.org/netdev/20261110174751.973464-1@gmail.com/
> - The datapath spec no longer puts a maximum on masks-cache-size. The
> generator does not turn a check into a policy for these families, and
> the kernel bound is an expression, so the declaration promised
> something the spec cannot express.
> - The docs no longer say what a dump does with a key, a ufid or another
> request attribute. A dump now has its own request list for each family,
> which states what it takes, so the sentences that repeated it are gone.
> The ufid docs record the minimum length the policy sets, and the key,
> actions, stats, used and tcp-flags docs say the attributes appear in
> replies as well as in notifications.
> - The series gains a third patch for gaps that predate it. The vport
> netnsid is signed in the kernel. The two dumps stop sharing a request
> list with their get operation, and four lists named attributes their
> handler never reads or sends. The vport get request can be answered by
> port number, and the vport new doc says an ifindex needs an internal
> vport. The vport spec declared family version 2 where the kernel
> registers 1.
> - That patch also declares what the kernel registers: all four ovs specs
> document the header struct and none of them a member of it, the vport
> name note names the header member the lookup uses, the options note
> says what a set returns, the packet execute operation gains the
> validate flags and the admin permission, and the ynl selftest stops
> printing a field the datapath reply does not carry.
> - Deleting one flow sends that flow to the family's multicast group, a
> flush sends nothing, and the set operations do the same for the object
> they change, which those op docs now say.
>
> [...]
Here is the summary with links:
- [net-next,v9,1/3] netlink: specs: add ovs_flow del and set operations
https://git.kernel.org/netdev/net-next/c/a07bb1cee2af
- [net-next,v9,2/3] netlink: specs: add ovs datapath and vport set operations
https://git.kernel.org/netdev/net-next/c/fa2ea983e25d
- [net-next,v9,3/3] netlink: specs: correct the ovs specs where they do not match the kernel
https://git.kernel.org/netdev/net-next/c/f53c4f7ecfcc
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-21 23:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 17:21 [PATCH net-next v9 0/3] netlink: specs: fill in the missing ovs operations Minxi Hou
2026-11-19 17:21 ` [PATCH net-next v9 1/3] netlink: specs: add ovs_flow del and set operations Minxi Hou
2026-11-19 17:21 ` [PATCH net-next v9 2/3] netlink: specs: add ovs datapath and vport " Minxi Hou
2026-11-19 17:21 ` [PATCH net-next v9 3/3] netlink: specs: correct the ovs specs where they do not match the kernel Minxi Hou
2026-11-21 23:50 ` patchwork-bot+netdevbpf [this message]
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=179530500653.1221130.3267976128355385798.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=donald.hunter@gmail.com \
--cc=echaudro@redhat.com \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=houminxi@gmail.com \
--cc=i.maximets@ovn.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