From: patchwork-bot+netdevbpf@kernel.org
To: Minxi Hou <houminxi@gmail.com>
Cc: netdev@vger.kernel.org, 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
Subject: Re: [PATCH net-next v5 0/2] Add OVS packet family YNL spec and unicast notification support
Date: Wed, 27 May 2026 00:30:11 +0000 [thread overview]
Message-ID: <177984181194.4027067.4872626990615141837.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260522174154.720293-1-houminxi@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 23 May 2026 01:41:52 +0800 you wrote:
> This series adds a YAML netlink spec for the OVS_PACKET_FAMILY genetlink
> family and a bind-only ntf_bind() helper for receiving unicast
> notifications.
>
> Changes in v5:
> - rebase on net-next to resolve conflict with Ilya Maximets'
> ntf_listen_all_nsid() (requested by Jakub Kicinski)
>
> [...]
Here is the summary with links:
- [net-next,v5,1/2] netlink: specs: add OVS packet family specification
https://git.kernel.org/netdev/net-next/c/b82bfddc46e2
- [net-next,v5,2/2] tools: ynl: add unicast notification receive support
https://git.kernel.org/netdev/net-next/c/b74e71b6a986
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-05-27 0:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 17:41 Minxi Hou
2026-05-22 17:41 ` [PATCH net-next v5 1/2] netlink: specs: add OVS packet family specification Minxi Hou
2026-05-22 17:41 ` [PATCH net-next v5 2/2] tools: ynl: add unicast notification receive support Minxi Hou
2026-05-27 0:30 ` 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=177984181194.4027067.4872626990615141837.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=houminxi@gmail.com \
--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
all inboxes | Powered by JetHome®