From: patchwork-bot+netdevbpf@kernel•org
To: Geliang Tang <geliang.tang@suse•com>
Cc: ast@kernel•org, daniel@iogearbox•net, andrii@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, revest@chromium•org,
jackmanb@chromium•org, matthieu.baerts@tessares•net,
martineau@kernel•org, davem@davemloft•net, edumazet@google•com,
kuba@kernel•org, pabeni@redhat•com, john.johansen@canonical•com,
paul@paul-moore•com, jmorris@namei•org, serge@hallyn•com,
stephen.smalley.work@gmail•com, eparis@parisplace•org,
mykolal@fb•com, shuah@kernel•org, horms@kernel•org,
bpf@vger•kernel.org, netdev@vger•kernel.org,
mptcp@lists•linux.dev, linux-security-module@vger•kernel.org,
selinux@vger•kernel.org, linux-kselftest@vger•kernel.org
Subject: Re: [PATCH bpf-next v14 0/4] bpf: Force to MPTCP
Date: Wed, 16 Aug 2023 19:00:28 +0000 [thread overview]
Message-ID: <169221242837.25657.8139131994909389115.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1692147782.git.geliang.tang@suse.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel•org>:
On Wed, 16 Aug 2023 09:11:55 +0800 you wrote:
> As is described in the "How to use MPTCP?" section in MPTCP wiki [1]:
>
> "Your app should create sockets with IPPROTO_MPTCP as the proto:
> ( socket(AF_INET, SOCK_STREAM, IPPROTO_MPTCP); ). Legacy apps can be
> forced to create and use MPTCP sockets instead of TCP ones via the
> mptcpize command bundled with the mptcpd daemon."
>
> [...]
Here is the summary with links:
- [bpf-next,v14,1/4] bpf: Add update_socket_protocol hook
https://git.kernel.org/bpf/bpf-next/c/0dd061a6a115
- [bpf-next,v14,2/4] selftests/bpf: Add two mptcp netns helpers
https://git.kernel.org/bpf/bpf-next/c/97c9c652089b
- [bpf-next,v14,3/4] selftests/bpf: Fix error checks of mptcp open_and_load
https://git.kernel.org/bpf/bpf-next/c/207746550262
- [bpf-next,v14,4/4] selftests/bpf: Add mptcpify test
https://git.kernel.org/bpf/bpf-next/c/ddba122428a7
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:[~2023-08-16 19:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 1:11 [PATCH bpf-next v14 0/4] bpf: Force to MPTCP Geliang Tang
2023-08-16 1:11 ` [PATCH bpf-next v14 1/4] bpf: Add update_socket_protocol hook Geliang Tang
2023-08-18 8:24 ` Geliang Tang
2023-08-18 15:26 ` Yonghong Song
2023-08-16 1:11 ` [PATCH bpf-next v14 2/4] selftests/bpf: Add two mptcp netns helpers Geliang Tang
2023-08-16 1:11 ` [PATCH bpf-next v14 3/4] selftests/bpf: Fix error checks of mptcp open_and_load Geliang Tang
2023-08-16 1:11 ` [PATCH bpf-next v14 4/4] selftests/bpf: Add mptcpify test Geliang Tang
2023-08-16 18:59 ` Martin KaFai Lau
2023-08-16 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=169221242837.25657.8139131994909389115.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=andrii@kernel$(echo .)org \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=eparis@parisplace$(echo .)org \
--cc=geliang.tang@suse$(echo .)com \
--cc=haoluo@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=jackmanb@chromium$(echo .)org \
--cc=jmorris@namei$(echo .)org \
--cc=john.fastabend@gmail$(echo .)com \
--cc=john.johansen@canonical$(echo .)com \
--cc=jolsa@kernel$(echo .)org \
--cc=kpsingh@kernel$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kselftest@vger$(echo .)kernel.org \
--cc=linux-security-module@vger$(echo .)kernel.org \
--cc=martin.lau@linux$(echo .)dev \
--cc=martineau@kernel$(echo .)org \
--cc=matthieu.baerts@tessares$(echo .)net \
--cc=mptcp@lists$(echo .)linux.dev \
--cc=mykolal@fb$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=paul@paul-moore$(echo .)com \
--cc=revest@chromium$(echo .)org \
--cc=sdf@google$(echo .)com \
--cc=selinux@vger$(echo .)kernel.org \
--cc=serge@hallyn$(echo .)com \
--cc=shuah@kernel$(echo .)org \
--cc=song@kernel$(echo .)org \
--cc=stephen.smalley.work@gmail$(echo .)com \
--cc=yhs@fb$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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