From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, martineau@kernel.org, geliang@kernel.org,
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@fomichev.me,
haoluo@google.com, jolsa@kernel.org, shuah@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
martin.lau@kernel.org
Subject: Re: [PATCH bpf-next/net v7 0/3] selftests/bpf: new MPTCP subflow subtest
Date: Tue, 01 Oct 2024 01:30:33 +0000 [thread overview]
Message-ID: <172774623351.4036978.717715429937152047.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240926-upstream-bpf-next-20240506-mptcp-subflow-test-v7-0-d26029e15cdd@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (net)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Thu, 26 Sep 2024 19:30:21 +0200 you wrote:
> In this series from Geliang, modifying MPTCP BPF selftests, we have:
>
> - A new MPTCP subflow BPF program setting socket options per subflow: it
> looks better to have this old test program in the BPF selftests to
> track regressions and to serve as example.
>
> Note: Nicolas is no longer working at Tessares, but he did this work
> while working for them, and his email address is no longer available.
>
> [...]
Here is the summary with links:
- [bpf-next/net,v7,1/3] selftests/bpf: Add mptcp subflow example
https://git.kernel.org/bpf/bpf-next/c/83752e12896a
- [bpf-next/net,v7,2/3] selftests/bpf: Add getsockopt to inspect mptcp subflow
https://git.kernel.org/bpf/bpf-next/c/cd19b885106e
- [bpf-next/net,v7,3/3] selftests/bpf: Add mptcp subflow subtest
https://git.kernel.org/bpf/bpf-next/c/9b85f11efa02
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-10-01 1:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 17:30 [PATCH bpf-next/net v7 0/3] selftests/bpf: new MPTCP subflow subtest Matthieu Baerts (NGI0)
2024-09-26 17:30 ` [PATCH bpf-next/net v7 1/3] selftests/bpf: Add mptcp subflow example Matthieu Baerts (NGI0)
2024-09-26 17:30 ` [PATCH bpf-next/net v7 2/3] selftests/bpf: Add getsockopt to inspect mptcp subflow Matthieu Baerts (NGI0)
2024-09-26 17:30 ` [PATCH bpf-next/net v7 3/3] selftests/bpf: Add mptcp subflow subtest Matthieu Baerts (NGI0)
2024-10-01 1:30 ` 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=172774623351.4036978.717715429937152047.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-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=martin.lau@linux.dev \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=mykolal@fb.com \
--cc=netdev@vger.kernel.org \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--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