From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, martineau@kernel.org, geliang@kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, yangang@kylinos.cn
Subject: Re: [PATCH net-next 0/7] selftests: mptcp: increase code coverage
Date: Tue, 06 May 2025 00:01:31 +0000 [thread overview]
Message-ID: <174648969104.970984.3012582895759124945.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250502-net-next-mptcp-sft-inc-cover-v1-0-68eec95898fb@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 02 May 2025 14:29:20 +0200 you wrote:
> Here are various patches slightly improving MPTCP code coverage:
>
> - Patch 1: avoid a harmless 'grep: write error' warning.
>
> - Patch 2: use getaddrinfo() with IPPROTO_MPTCP in more places.
>
> - Patch 3-6: prepare and add support to get info for a specific subflow
> when giving the 5-tuple.
>
> [...]
Here is the summary with links:
- [net-next,1/7] selftests: mptcp: info: hide 'grep: write error' warnings
https://git.kernel.org/netdev/net-next/c/6d0eb15c6501
- [net-next,2/7] selftests: mptcp: sockopt: use IPPROTO_MPTCP for getaddrinfo
https://git.kernel.org/netdev/net-next/c/dd367e81b79a
- [net-next,3/7] selftests: mptcp: add struct params in mptcp_diag
https://git.kernel.org/netdev/net-next/c/cd732d5110a2
- [net-next,4/7] selftests: mptcp: refactor send_query parameters for code clarity
https://git.kernel.org/netdev/net-next/c/3fea468dca4f
- [net-next,5/7] selftests: mptcp: refactor NLMSG handling with 'proto'
https://git.kernel.org/netdev/net-next/c/caa6811ccaed
- [net-next,6/7] selftests: mptcp: add helpers to get subflow_info
https://git.kernel.org/netdev/net-next/c/c7ac7452df70
- [net-next,7/7] selftests: mptcp: add chk_sublfow in diag.sh
https://git.kernel.org/netdev/net-next/c/110f8f77fd8d
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:[~2025-05-06 0:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 12:29 [PATCH net-next 0/7] selftests: mptcp: increase code coverage Matthieu Baerts (NGI0)
2025-05-02 12:29 ` [PATCH net-next 1/7] selftests: mptcp: info: hide 'grep: write error' warnings Matthieu Baerts (NGI0)
2025-05-02 12:29 ` [PATCH net-next 2/7] selftests: mptcp: sockopt: use IPPROTO_MPTCP for getaddrinfo Matthieu Baerts (NGI0)
2025-05-02 12:29 ` [PATCH net-next 3/7] selftests: mptcp: add struct params in mptcp_diag Matthieu Baerts (NGI0)
2025-05-02 12:29 ` [PATCH net-next 4/7] selftests: mptcp: refactor send_query parameters for code clarity Matthieu Baerts (NGI0)
2025-05-02 12:29 ` [PATCH net-next 5/7] selftests: mptcp: refactor NLMSG handling with 'proto' Matthieu Baerts (NGI0)
2025-05-02 12:29 ` [PATCH net-next 6/7] selftests: mptcp: add helpers to get subflow_info Matthieu Baerts (NGI0)
2025-05-02 12:29 ` [PATCH net-next 7/7] selftests: mptcp: add chk_sublfow in diag.sh Matthieu Baerts (NGI0)
2025-05-06 0:01 ` 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=174648969104.970984.3012582895759124945.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=yangang@kylinos.cn \
/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.