From: patchwork-bot+netdevbpf@kernel.org
To: Eyal Birger <eyal.birger@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, steffen.klassert@secunet.com,
herbert@gondor.apana.org.au, andrii@kernel.org,
daniel@iogearbox.net, nicolas.dichtel@6wind.com,
razor@blackwall.org, mykolal@fb.com, ast@kernel.org,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, shuah@kernel.org,
liuhangbin@gmail.com, lixiaoyan@google.com, jtoppins@redhat.com,
kuniyu@amazon.co.jp, netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next,v6 0/4] xfrm: interface: Add unstable helpers for XFRM metadata
Date: Tue, 06 Dec 2022 07:10:16 +0000 [thread overview]
Message-ID: <167031061689.3006.16415663365727591503.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221203084659.1837829-1-eyal.birger@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Sat, 3 Dec 2022 10:46:55 +0200 you wrote:
> This patch series adds xfrm metadata helpers using the unstable kfunc
> call interface for the TC-BPF hooks.
>
> This allows steering traffic towards different IPsec connections based
> on logic implemented in bpf programs.
>
> The helpers are integrated into the xfrm_interface module. For this
> purpose the main functionality of this module is moved to
> xfrm_interface_core.c.
>
> [...]
Here is the summary with links:
- [bpf-next,v6,1/4] xfrm: interface: rename xfrm_interface.c to xfrm_interface_core.c
https://git.kernel.org/bpf/bpf-next/c/ee9a113ab634
- [bpf-next,v6,2/4] xfrm: interface: Add unstable helpers for setting/getting XFRM metadata from TC-BPF
https://git.kernel.org/bpf/bpf-next/c/94151f5aa966
- [bpf-next,v6,3/4] tools: add IFLA_XFRM_COLLECT_METADATA to uapi/linux/if_link.h
https://git.kernel.org/bpf/bpf-next/c/4f4ac4d9106e
- [bpf-next,v6,4/4] selftests/bpf: add xfrm_info tests
https://git.kernel.org/bpf/bpf-next/c/90a3a05eb33f
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:[~2022-12-06 7:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-03 8:46 [PATCH bpf-next,v6 0/4] xfrm: interface: Add unstable helpers for XFRM metadata Eyal Birger
2022-12-03 8:46 ` [PATCH bpf-next,v6 1/4] xfrm: interface: rename xfrm_interface.c to xfrm_interface_core.c Eyal Birger
2022-12-03 8:46 ` [PATCH bpf-next,v6 2/4] xfrm: interface: Add unstable helpers for setting/getting XFRM metadata from TC-BPF Eyal Birger
2022-12-03 8:46 ` [PATCH bpf-next,v6 3/4] tools: add IFLA_XFRM_COLLECT_METADATA to uapi/linux/if_link.h Eyal Birger
2022-12-03 8:46 ` [PATCH bpf-next,v6 4/4] selftests/bpf: add xfrm_info tests Eyal Birger
2022-12-06 7:13 ` Martin KaFai Lau
2022-12-06 7:10 ` 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=167031061689.3006.16415663365727591503.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eyal.birger@gmail.com \
--cc=haoluo@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=jtoppins@redhat.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.co.jp \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=lixiaoyan@google.com \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=yhs@fb.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.