From: patchwork-bot+netdevbpf@kernel.org
To: Allison Henderson <achender@kernel.org>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, edumazet@google.com,
kuba@kernel.org, horms@kernel.org, linux-rdma@vger.kernel.org,
linux-kselftest@vger.kernel.org, shuah@kernel.org
Subject: Re: [PATCH net-next v1 0/3] Log clean up and TAP follow ups
Date: Sun, 10 May 2026 17:30:10 +0000 [thread overview]
Message-ID: <177843421005.1439575.2959535937305070033.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260507233213.556182-1-achender@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 7 May 2026 16:32:10 -0700 you wrote:
> Hi all,
>
> This is a follow up series to the "Log collection, TAP compliance and
> cleanups" set. The sashiko report had made some points that I thought
> was worth addressing. This patch set fixes a few more TAP compliance
> prints in the check_gcov* routines. Also since the user must now pass
> in the log folder to collect logs, log clean up is tightened to only
> remove rds* prefixed artifacts instead of the entire folder. Lastly a
> the signal handler alarm should be disarmed after the completes to
> avoid multiple calls to the stop_pcaps routine.
>
> [...]
Here is the summary with links:
- [net-next,v1,1/3] selftests: rds: Fix stale log clean up
https://git.kernel.org/netdev/net-next/c/4840467c84de
- [net-next,v1,2/3] selftests: rds: Fix TAP-prefixed prints in check_gcov*
https://git.kernel.org/netdev/net-next/c/490778834a42
- [net-next,v1,3/3] selftests: rds: Disarm signal alarm on test completion
https://git.kernel.org/netdev/net-next/c/08724ab1dc17
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:[~2026-05-10 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 23:32 [PATCH net-next v1 0/3] Log clean up and TAP follow ups Allison Henderson
2026-05-07 23:32 ` [PATCH net-next v1 1/3] selftests: rds: Fix stale log clean up Allison Henderson
2026-05-07 23:32 ` [PATCH net-next v1 2/3] selftests: rds: Fix TAP-prefixed prints in check_gcov* Allison Henderson
2026-05-07 23:32 ` [PATCH net-next v1 3/3] selftests: rds: Disarm signal alarm on test completion Allison Henderson
2026-05-10 17:30 ` 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=177843421005.1439575.2959535937305070033.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=achender@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/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