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 v6 0/6] use network helpers, part 7
Date: Fri, 21 Jun 2024 03:50:30 +0000 [thread overview]
Message-ID: <171894183068.10505.4717563449095144066.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1718932493.git.tanggeliang@kylinos.cn>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 21 Jun 2024 10:15:57 +0800 you wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> v6:
> - update ASSERT strings in patch 4 as Eduard suggested. (thanks)
>
> v5:
> - update patch 1, add getsockopt(SO_PROTOCOL) in connect_to_fd() to
> fix errors reported by CI.
>
> [...]
Here is the summary with links:
- [bpf-next,v6,1/6] selftests/bpf: Drop type from network_helper_opts
https://git.kernel.org/bpf/bpf-next/c/34ad6ec97252
- [bpf-next,v6,2/6] selftests/bpf: Use connect_to_addr in connect_to_fd_opt
https://git.kernel.org/bpf/bpf-next/c/08a5206240d3
- [bpf-next,v6,3/6] selftests/bpf: Add client_socket helper
https://git.kernel.org/bpf/bpf-next/c/bbca57aa378b
- [bpf-next,v6,4/6] selftests/bpf: Drop noconnect from network_helper_opts
https://git.kernel.org/bpf/bpf-next/c/7f0d5140a6d6
- [bpf-next,v6,5/6] selftests/bpf: Use start_server_str in mptcp
https://git.kernel.org/bpf/bpf-next/c/fb69f71cf585
- [bpf-next,v6,6/6] selftests/bpf: Use start_server_str in test_tcp_check_syncookie_user
https://git.kernel.org/bpf/bpf-next/c/8cab7cdcf5ae
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-06-21 3:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 2:15 [PATCH bpf-next v6 0/6] use network helpers, part 7 Geliang Tang
2024-06-21 2:15 ` [PATCH bpf-next v6 1/6] selftests/bpf: Drop type from network_helper_opts Geliang Tang
2024-06-21 2:15 ` [PATCH bpf-next v6 2/6] selftests/bpf: Use connect_to_addr in connect_to_fd_opt Geliang Tang
2024-06-21 2:16 ` [PATCH bpf-next v6 3/6] selftests/bpf: Add client_socket helper Geliang Tang
2024-06-21 2:16 ` [PATCH bpf-next v6 4/6] selftests/bpf: Drop noconnect from network_helper_opts Geliang Tang
2024-06-21 2:16 ` [PATCH bpf-next v6 5/6] selftests/bpf: Use start_server_str in mptcp Geliang Tang
2024-06-21 2:16 ` [PATCH bpf-next v6 6/6] selftests/bpf: Use start_server_str in test_tcp_check_syncookie_user Geliang Tang
2024-06-21 3:50 ` 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=171894183068.10505.4717563449095144066.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