From: patchwork-bot+netdevbpf@kernel.org
To: Geliang Tang <geliang@kernel.org>
Cc: andrii@kernel.org, eddyz87@gmail.com, mykolal@fb.com,
ast@kernel.org, daniel@iogearbox.net, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, shuah@kernel.org,
tanggeliang@kylinos.cn, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next v11 0/9] use network helpers, part 8
Date: Wed, 10 Jul 2024 19:00:38 +0000 [thread overview]
Message-ID: <172063803876.15275.14385138929518529684.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1720515893.git.tanggeliang@kylinos.cn>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Tue, 9 Jul 2024 17:16:16 +0800 you wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> v11:
> - new patches 2, 4, 6.
> - drop expect_errno from network_helper_opts as Eduard and Martin
> suggested.
> - drop sockmap_ktls patches from this set.
> - add a new helper connect_fd_to_addr_str.
>
> [...]
Here is the summary with links:
- [bpf-next,v11,1/9] selftests/bpf: Add backlog for network_helper_opts
https://git.kernel.org/bpf/bpf-next/c/a3016a27cea8
- [bpf-next,v11,2/9] selftests/bpf: Add ASSERT_OK_FD macro
https://git.kernel.org/bpf/bpf-next/c/7046345d48ad
- [bpf-next,v11,3/9] selftests/bpf: Close fd in error path in drop_on_reuseport
https://git.kernel.org/bpf/bpf-next/c/adae187ebedc
- [bpf-next,v11,4/9] selftests/bpf: Use start_server_str in sk_lookup
https://git.kernel.org/bpf/bpf-next/c/14fc6fcd35e7
- [bpf-next,v11,5/9] selftests/bpf: Use start_server_addr in sk_lookup
https://git.kernel.org/bpf/bpf-next/c/d9810c43f660
- [bpf-next,v11,6/9] selftests/bpf: Use connect_fd_to_fd in sk_lookup
https://git.kernel.org/bpf/bpf-next/c/9004054b1629
- [bpf-next,v11,7/9] selftests/bpf: Add connect_fd_to_addr_str helper
(no matching commit)
- [bpf-next,v11,8/9] selftests/bpf: Use connect_fd_to_addr_str in sk_lookup
(no matching commit)
- [bpf-next,v11,9/9] selftests/bpf: Drop make_socket in sk_lookup
(no matching commit)
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:[~2024-07-10 19:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 9:16 [PATCH bpf-next v11 0/9] use network helpers, part 8 Geliang Tang
2024-07-09 9:16 ` [PATCH bpf-next v11 1/9] selftests/bpf: Add backlog for network_helper_opts Geliang Tang
2024-07-09 9:16 ` [PATCH bpf-next v11 2/9] selftests/bpf: Add ASSERT_OK_FD macro Geliang Tang
2024-07-10 19:00 ` Martin KaFai Lau
2024-07-09 9:16 ` [PATCH bpf-next v11 3/9] selftests/bpf: Close fd in error path in drop_on_reuseport Geliang Tang
2024-07-10 19:02 ` Martin KaFai Lau
2024-07-09 9:16 ` [PATCH bpf-next v11 4/9] selftests/bpf: Use start_server_str in sk_lookup Geliang Tang
2024-07-09 9:16 ` [PATCH bpf-next v11 5/9] selftests/bpf: Use start_server_addr " Geliang Tang
2024-07-09 9:16 ` [PATCH bpf-next v11 6/9] selftests/bpf: Use connect_fd_to_fd " Geliang Tang
2024-07-10 19:04 ` Martin KaFai Lau
2024-07-09 9:16 ` [PATCH bpf-next v11 7/9] selftests/bpf: Add connect_fd_to_addr_str helper Geliang Tang
2024-07-10 19:20 ` Martin KaFai Lau
2024-07-09 9:16 ` [PATCH bpf-next v11 8/9] selftests/bpf: Use connect_fd_to_addr_str in sk_lookup Geliang Tang
2024-07-09 9:16 ` [PATCH bpf-next v11 9/9] selftests/bpf: Drop make_socket " Geliang Tang
2024-07-10 19:00 ` 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=172063803876.15275.14385138929518529684.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=eddyz87@gmail.com \
--cc=geliang@kernel.org \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=tanggeliang@kylinos.cn \
--cc=yonghong.song@linux.dev \
/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