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, shuah@kernel.org, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
tanggeliang@kylinos.cn
Subject: Re: [PATCH net-next 00/11] selftests: mptcp: cleanups and 'ip mptcp' support
Date: Mon, 08 Apr 2024 11:00:34 +0000 [thread overview]
Message-ID: <171257403465.26748.462026930608140771.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240405-upstream-net-next-20240405-mptcp-selftests-refactoring-v1-0-eabc9b960966@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 05 Apr 2024 12:52:04 +0200 you wrote:
> Here are some patches from Geliang, doing different cleanups, and
> supporting 'ip mptcp' in more MPTCP selftests.
>
> Patch 1 checks that TC is available in selftests requiring it.
>
> Patch 2 adds 'ms' units in TC commands, to avoid confusions.
>
> [...]
Here is the summary with links:
- [net-next,01/11] selftests: mptcp: add tc check for check_tools
https://git.kernel.org/netdev/net-next/c/f30b04cacd85
- [net-next,02/11] selftests: mptcp: add ms units for tc-netem delay
https://git.kernel.org/netdev/net-next/c/9109853a388b
- [net-next,03/11] selftests: mptcp: export ip_mptcp to mptcp_lib
https://git.kernel.org/netdev/net-next/c/29aa32fee7d0
- [net-next,04/11] selftests: mptcp: netlink: add 'limits' helpers
https://git.kernel.org/netdev/net-next/c/3188309c8ceb
- [net-next,05/11] selftests: mptcp: add {get,format}_endpoint(s) helpers
https://git.kernel.org/netdev/net-next/c/0d16ed0c2e74
- [net-next,06/11] selftests: mptcp: netlink: add change_address helper
https://git.kernel.org/netdev/net-next/c/b79e51c99949
- [net-next,07/11] selftests: mptcp: join: update endpoint ops
https://git.kernel.org/netdev/net-next/c/571d79664a4a
- [net-next,08/11] selftests: mptcp: export pm_nl endpoint ops
https://git.kernel.org/netdev/net-next/c/441c6be9ae28
- [net-next,09/11] selftests: mptcp: use pm_nl endpoint ops
https://git.kernel.org/netdev/net-next/c/c99d57d0007a
- [net-next,10/11] selftests: mptcp: ip_mptcp option for more scripts
https://git.kernel.org/netdev/net-next/c/0cef6fcac24d
- [net-next,11/11] selftests: mptcp: netlink: drop disable=SC2086
https://git.kernel.org/netdev/net-next/c/6eaeda12dc77
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-04-08 11:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 10:52 [PATCH net-next 00/11] selftests: mptcp: cleanups and 'ip mptcp' support Matthieu Baerts (NGI0)
2024-04-05 10:52 ` [PATCH net-next 01/11] selftests: mptcp: add tc check for check_tools Matthieu Baerts (NGI0)
2024-04-05 10:52 ` [PATCH net-next 02/11] selftests: mptcp: add ms units for tc-netem delay Matthieu Baerts (NGI0)
2024-04-05 10:52 ` [PATCH net-next 03/11] selftests: mptcp: export ip_mptcp to mptcp_lib Matthieu Baerts (NGI0)
2024-04-05 10:52 ` [PATCH net-next 04/11] selftests: mptcp: netlink: add 'limits' helpers Matthieu Baerts (NGI0)
2024-04-05 10:52 ` [PATCH net-next 05/11] selftests: mptcp: add {get,format}_endpoint(s) helpers Matthieu Baerts (NGI0)
2024-04-05 10:52 ` [PATCH net-next 06/11] selftests: mptcp: netlink: add change_address helper Matthieu Baerts (NGI0)
2024-04-05 10:52 ` [PATCH net-next 07/11] selftests: mptcp: join: update endpoint ops Matthieu Baerts (NGI0)
2024-04-05 10:52 ` [PATCH net-next 08/11] selftests: mptcp: export pm_nl " Matthieu Baerts (NGI0)
2024-04-05 10:52 ` [PATCH net-next 09/11] selftests: mptcp: use " Matthieu Baerts (NGI0)
2024-04-05 10:52 ` [PATCH net-next 10/11] selftests: mptcp: ip_mptcp option for more scripts Matthieu Baerts (NGI0)
2024-04-05 10:52 ` [PATCH net-next 11/11] selftests: mptcp: netlink: drop disable=SC2086 Matthieu Baerts (NGI0)
2024-04-08 11: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=171257403465.26748.462026930608140771.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@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=tanggeliang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).