From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, shuah@kernel.org,
martineau@kernel.org, geliang@kernel.org, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
tanggeliang@kylinos.cn
Subject: Re: [PATCH net-next 0/6] selftests: mptcp: use net/lib.sh to manage netns
Date: Wed, 12 Jun 2024 03:00:38 +0000 [thread overview]
Message-ID: <171816123840.11889.13593974623249727089.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240607-upstream-net-next-20240607-selftests-mptcp-net-lib-v1-0-e36986faac94@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 07 Jun 2024 18:31:01 +0200 you wrote:
> The goal of this series is to use helpers from net/lib.sh with MPTCP
> selftests.
>
> - Patches 1 to 4 are some clean-ups and preparation in net/lib.sh:
>
> - Patch 1 simplifies the code handling errexit by ignoring possible
> errors instead of disabling errexit temporary.
>
> [...]
Here is the summary with links:
- [net-next,1/6] selftests: net: lib: ignore possible errors
https://git.kernel.org/netdev/net-next/c/7e0620bc6a5e
- [net-next,2/6] selftests: net: lib: remove ns from list after clean-up
https://git.kernel.org/netdev/net-next/c/92fe5670271a
- [net-next,3/6] selftests: net: lib: do not set ns var as readonly
https://git.kernel.org/netdev/net-next/c/577db6bd5750
- [net-next,4/6] selftests: net: lib: remove 'ns' var in setup_ns
https://git.kernel.org/netdev/net-next/c/f8a2d2f874b7
- [net-next,5/6] selftests: mptcp: lib: use setup/cleanup_ns helpers
https://git.kernel.org/netdev/net-next/c/f265d3119a29
- [net-next,6/6] selftests: mptcp: lib: use wait_local_port_listen helper
https://git.kernel.org/netdev/net-next/c/1af3bc912eac
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-06-12 3:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 16:31 [PATCH net-next 0/6] selftests: mptcp: use net/lib.sh to manage netns Matthieu Baerts (NGI0)
2024-06-07 16:31 ` [PATCH net-next 1/6] selftests: net: lib: ignore possible errors Matthieu Baerts (NGI0)
2024-06-07 16:31 ` [PATCH net-next 2/6] selftests: net: lib: remove ns from list after clean-up Matthieu Baerts (NGI0)
2024-06-14 10:40 ` Simon Horman
2024-06-14 14:42 ` Matthieu Baerts
2024-06-15 7:40 ` Simon Horman
2024-06-07 16:31 ` [PATCH net-next 3/6] selftests: net: lib: do not set ns var as readonly Matthieu Baerts (NGI0)
2024-06-07 16:31 ` [PATCH net-next 4/6] selftests: net: lib: remove 'ns' var in setup_ns Matthieu Baerts (NGI0)
2024-06-07 16:31 ` [PATCH net-next 5/6] selftests: mptcp: lib: use setup/cleanup_ns helpers Matthieu Baerts (NGI0)
2024-06-07 16:31 ` [PATCH net-next 6/6] selftests: mptcp: lib: use wait_local_port_listen helper Matthieu Baerts (NGI0)
2024-06-12 3: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=171816123840.11889.13593974623249727089.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 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.