From: patchwork-bot+netdevbpf@kernel.org
To: Florian Westphal <fw@strlen.de>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, dxu@dxuuu.xyz, qde@naccy.de
Subject: Re: [PATCH bpf-next v5 0/7] bpf: add netfilter program type
Date: Fri, 21 Apr 2023 18:50:21 +0000 [thread overview]
Message-ID: <168210302187.11240.7792947856131351121.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230421170300.24115-1-fw@strlen.de>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 21 Apr 2023 19:02:53 +0200 you wrote:
> Changes since last version:
> - rework test case in last patch wrt. ctx->skb dereference etc (Alexei)
> - pacify bpf ci tests, netfilter program type missed string translation
> in libbpf helper.
>
> This still uses runtime btf walk rather than extending
> the btf trace array as Alexei suggested, I would do this later (or someone else can).
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/7] bpf: add bpf_link support for BPF_NETFILTER programs
https://git.kernel.org/bpf/bpf-next/c/84601d6ee68a
- [bpf-next,v5,2/7] bpf: minimal support for programs hooked into netfilter framework
https://git.kernel.org/bpf/bpf-next/c/fd9c663b9ad6
- [bpf-next,v5,3/7] netfilter: nfnetlink hook: dump bpf prog id
https://git.kernel.org/bpf/bpf-next/c/506a74db7e01
- [bpf-next,v5,4/7] netfilter: disallow bpf hook attachment at same priority
https://git.kernel.org/bpf/bpf-next/c/0bdc6da88f5b
- [bpf-next,v5,5/7] tools: bpftool: print netfilter link info
(no matching commit)
- [bpf-next,v5,6/7] bpf: add test_run support for netfilter program type
https://git.kernel.org/bpf/bpf-next/c/2b99ef22e0d2
- [bpf-next,v5,7/7] selftests/bpf: add missing netfilter return value and ctx access tests
https://git.kernel.org/bpf/bpf-next/c/006c0e44ed92
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:[~2023-04-21 18:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 17:02 [PATCH bpf-next v5 0/7] bpf: add netfilter program type Florian Westphal
2023-04-21 17:02 ` [PATCH bpf-next v5 1/7] bpf: add bpf_link support for BPF_NETFILTER programs Florian Westphal
2023-04-27 4:51 ` Andrii Nakryiko
2023-04-27 9:10 ` Florian Westphal
2023-04-27 22:21 ` Andrii Nakryiko
2023-04-28 16:54 ` Quentin Deslandes
2023-04-28 21:18 ` Andrii Nakryiko
2023-04-21 17:02 ` [PATCH bpf-next v5 2/7] bpf: minimal support for programs hooked into netfilter framework Florian Westphal
2023-04-21 17:02 ` [PATCH bpf-next v5 3/7] netfilter: nfnetlink hook: dump bpf prog id Florian Westphal
2023-04-21 17:02 ` [PATCH bpf-next v5 4/7] netfilter: disallow bpf hook attachment at same priority Florian Westphal
2023-04-21 17:02 ` [PATCH bpf-next v5 5/7] tools: bpftool: print netfilter link info Florian Westphal
2023-04-21 17:02 ` [PATCH bpf-next v5 6/7] bpf: add test_run support for netfilter program type Florian Westphal
2023-04-21 17:03 ` [PATCH bpf-next v5 7/7] selftests/bpf: add missing netfilter return value and ctx access tests Florian Westphal
2023-04-21 18:50 ` patchwork-bot+netdevbpf [this message]
2023-04-21 20:26 ` [PATCH bpf-next v5 0/7] bpf: add netfilter program type Daniel Xu
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=168210302187.11240.7792947856131351121.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dxu@dxuuu.xyz \
--cc=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=qde@naccy.de \
/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.