From: patchwork-bot+netdevbpf@kernel.org
To: Guillaume Nault <gnault@redhat.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
dsahern@gmail.com, vfedorenko@novek.ru, shuah@kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net 0/2] selftests: pmtu.sh: Fix cleanup of processes launched in subshell.
Date: Thu, 10 Mar 2022 05:00:10 +0000 [thread overview]
Message-ID: <164688841097.28597.13633737666030841874.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1646776561.git.gnault@redhat.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 8 Mar 2022 23:14:57 +0100 you wrote:
> Depending on the options used, pmtu.sh may launch tcpdump and nettest
> processes in the background. However it fails to clean them up after
> the tests complete.
>
> Patch 1 allows the cleanup() function to read the list of PIDs launched
> by the tests.
> Patch 2 fixes the way the nettest PIDs are retrieved.
>
> [...]
Here is the summary with links:
- [net,1/2] selftests: pmtu.sh: Kill tcpdump processes launched by subshell.
https://git.kernel.org/netdev/net/c/18dfc667550f
- [net,2/2] selftests: pmtu.sh: Kill nettest processes launched in subshell.
https://git.kernel.org/netdev/net/c/94a4a4fe4c69
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:[~2022-03-10 5:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 22:14 [PATCH net 0/2] selftests: pmtu.sh: Fix cleanup of processes launched in subshell Guillaume Nault
2022-03-08 22:15 ` [PATCH net 1/2] selftests: pmtu.sh: Kill tcpdump processes launched by subshell Guillaume Nault
2022-03-08 22:15 ` [PATCH net 2/2] selftests: pmtu.sh: Kill nettest processes launched in subshell Guillaume Nault
2022-03-08 23:51 ` [PATCH net 0/2] selftests: pmtu.sh: Fix cleanup of " Shuah Khan
2022-03-09 0:55 ` Guillaume Nault
2022-03-10 5: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=164688841097.28597.13633737666030841874.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=gnault@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=vfedorenko@novek.ru \
/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