From: patchwork-bot+netdevbpf@kernel.org
To: Mat Martineau <martineau@kernel.org>
Cc: matthieu.baerts@tessares.net, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, mptcp@lists.linux.dev,
geliang.tang@suse.com, shamrocklee@posteo.net
Subject: Re: [PATCH net-next 0/8] selftests: mptcp: Refactoring and minor fixes
Date: Sat, 24 Jun 2023 22:40:24 +0000 [thread overview]
Message-ID: <168764642457.414.3013119023826690334.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230623-send-net-next-20230623-v1-0-a883213c8ba9@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 23 Jun 2023 10:34:06 -0700 you wrote:
> Patch 1 moves code around for clarity and improved code reuse.
>
> Patch 2 makes use of new MPTCP info that consolidates MPTCP-level and
> subflow-level information.
>
> Patches 3-7 refactor code to favor limited-scope environment vars over
> optional parameters.
>
> [...]
Here is the summary with links:
- [net-next,1/8] selftests: mptcp: test userspace pm out of transfer
https://git.kernel.org/netdev/net-next/c/4369c198e599
- [net-next,2/8] selftests: mptcp: check subflow and addr infos
https://git.kernel.org/netdev/net-next/c/d7ced753aa85
- [net-next,3/8] selftests: mptcp: set FAILING_LINKS in run_tests
https://git.kernel.org/netdev/net-next/c/be7e9786c915
- [net-next,4/8] selftests: mptcp: drop test_linkfail parameter
https://git.kernel.org/netdev/net-next/c/0c93af1f8907
- [net-next,5/8] selftests: mptcp: drop addr_nr_ns1/2 parameters
https://git.kernel.org/netdev/net-next/c/595ef566a2ef
- [net-next,6/8] selftests: mptcp: drop sflags parameter
https://git.kernel.org/netdev/net-next/c/1534f87ee0dc
- [net-next,7/8] selftests: mptcp: add pm_nl_set_endpoint helper
https://git.kernel.org/netdev/net-next/c/9e9d176df8e9
- [net-next,8/8] selftests: mptcp: connect: fix comment typo
https://git.kernel.org/netdev/net-next/c/e6b8a78ea266
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-06-24 22:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 17:34 [PATCH net-next 0/8] selftests: mptcp: Refactoring and minor fixes Mat Martineau
2023-06-23 17:34 ` [PATCH net-next 1/8] selftests: mptcp: test userspace pm out of transfer Mat Martineau
2023-06-23 17:34 ` [PATCH net-next 2/8] selftests: mptcp: check subflow and addr infos Mat Martineau
2023-06-23 17:34 ` [PATCH net-next 3/8] selftests: mptcp: set FAILING_LINKS in run_tests Mat Martineau
2023-06-23 17:34 ` [PATCH net-next 4/8] selftests: mptcp: drop test_linkfail parameter Mat Martineau
2023-06-23 17:34 ` [PATCH net-next 5/8] selftests: mptcp: drop addr_nr_ns1/2 parameters Mat Martineau
2023-06-23 17:34 ` [PATCH net-next 6/8] selftests: mptcp: drop sflags parameter Mat Martineau
2023-06-23 17:34 ` [PATCH net-next 7/8] selftests: mptcp: add pm_nl_set_endpoint helper Mat Martineau
2023-06-23 17:34 ` [PATCH net-next 8/8] selftests: mptcp: connect: fix comment typo Mat Martineau
2023-06-24 22:40 ` 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=168764642457.414.3013119023826690334.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang.tang@suse.com \
--cc=kuba@kernel.org \
--cc=martineau@kernel.org \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shamrocklee@posteo.net \
/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.