From: patchwork-bot+netdevbpf@kernel.org
To: Florian Westphal <fw@strlen.de>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, willemb@google.com,
pablo@netfilter.org
Subject: Re: [PATCH net-next v2 0/2] net: flow dissector: allow explicit passing of netns
Date: Wed, 12 Jun 2024 22:00:30 +0000 [thread overview]
Message-ID: <171822963079.31898.17243541144080148140.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240608221057.16070-1-fw@strlen.de>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 9 Jun 2024 00:10:38 +0200 you wrote:
> Change since last version:
> fix kdoc comment warning reported by kbuild robot, no other changes,
> thus retaining RvB tags from Eric and Willem.
> v1: https://lore.kernel.org/netdev/20240607083205.3000-1-fw@strlen.de/
>
> Years ago flow dissector gained ability to delegate flow dissection
> to a bpf program, scoped per netns.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: add and use skb_get_hash_net
https://git.kernel.org/netdev/net-next/c/b975d3ee5962
- [net-next,v2,2/2] net: add and use __skb_get_hash_symmetric_net
https://git.kernel.org/netdev/net-next/c/d1dab4f71d37
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-06-12 22:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-08 22:10 [PATCH net-next v2 0/2] net: flow dissector: allow explicit passing of netns Florian Westphal
2024-06-08 22:10 ` [PATCH net-next v2 1/2] net: add and use skb_get_hash_net Florian Westphal
2024-06-08 22:10 ` [PATCH net-next v2 2/2] net: add and use __skb_get_hash_symmetric_net Florian Westphal
2024-06-09 5:06 ` [PATCH net-next v2 0/2] net: flow dissector: allow explicit passing of netns Eric Dumazet
2024-06-12 22:00 ` patchwork-bot+netdevbpf [this message]
2024-06-26 23:49 ` Pablo Neira Ayuso
2024-06-27 10:20 ` Paolo Abeni
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=171822963079.31898.17243541144080148140.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=willemb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.