public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
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 v3 00/10] selftests: rds: Log collection, TAP compliance and cleanups
Date: Wed, 06 May 2026 02:30:31 +0000	[thread overview]
Message-ID: <177803463154.2357425.4119848919465141274.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260504054143.4027538-1-achender@kernel.org>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Sun,  3 May 2026 22:41:33 -0700 you wrote:
> This series is a set of bug fixes and improvements for the rds
> selftests.
> 
> Patch 1 bumps the kselftest timeout from 400s to 800s. The original
> limit was developed against a lean config, but the kselftest harness
> counts boot time and gcov log collection against the limit, so a
> default config with gcov enabled needs more headroom.
> 
> [...]

Here is the summary with links:
  - [net-next,v3,01/10] selftests: rds: Increase selftest timeout
    https://git.kernel.org/netdev/net-next/c/94720e01f5bb
  - [net-next,v3,02/10] selftests: rds: Update USAGE string for run.sh
    https://git.kernel.org/netdev/net-next/c/4781c8b037a8
  - [net-next,v3,03/10] selftests: rds: Fix more pylint errors
    https://git.kernel.org/netdev/net-next/c/5bdd59f90633
  - [net-next,v3,04/10] selftests: rds: Add timeout flag to run.sh
    https://git.kernel.org/netdev/net-next/c/7d6a32e7cb45
  - [net-next,v3,05/10] selftests: rds: Add RDS_LOG_DIR env variable
    https://git.kernel.org/netdev/net-next/c/ad070d903759
  - [net-next,v3,06/10] selftests: rds: Add SUDO_USER env variable
    https://git.kernel.org/netdev/net-next/c/d601239dcc26
  - [net-next,v3,07/10] selftests: rds: Remove tmp pcaps
    https://git.kernel.org/netdev/net-next/c/c726bc68fffd
  - [net-next,v3,08/10] selftests: rds: Stop tcpdump on timeout
    https://git.kernel.org/netdev/net-next/c/ec91483634fe
  - [net-next,v3,09/10] selftests: rds: Fix gcov collection
    https://git.kernel.org/netdev/net-next/c/c8781c61fd60
  - [net-next,v3,10/10] selftests: rds: Make rds selftests TAP compliant
    https://git.kernel.org/netdev/net-next/c/06d5c34517e0

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-05-06  2:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-04  5:41 [PATCH net-next v3 00/10] selftests: rds: Log collection, TAP compliance and cleanups Allison Henderson
2026-05-04  5:41 ` [PATCH net-next v3 01/10] selftests: rds: Increase selftest timeout Allison Henderson
2026-05-04  5:41 ` [PATCH net-next v3 02/10] selftests: rds: Update USAGE string for run.sh Allison Henderson
2026-05-04  5:41 ` [PATCH net-next v3 03/10] selftests: rds: Fix more pylint errors Allison Henderson
2026-05-04  5:41 ` [PATCH net-next v3 04/10] selftests: rds: Add timeout flag to run.sh Allison Henderson
2026-05-04  5:41 ` [PATCH net-next v3 05/10] selftests: rds: Add RDS_LOG_DIR env variable Allison Henderson
2026-05-04  5:41 ` [PATCH net-next v3 06/10] selftests: rds: Add SUDO_USER " Allison Henderson
2026-05-04  5:41 ` [PATCH net-next v3 07/10] selftests: rds: Remove tmp pcaps Allison Henderson
2026-05-04  5:41 ` [PATCH net-next v3 08/10] selftests: rds: Stop tcpdump on timeout Allison Henderson
2026-05-04  5:41 ` [PATCH net-next v3 09/10] selftests: rds: Fix gcov collection Allison Henderson
2026-05-04  5:41 ` [PATCH net-next v3 10/10] selftests: rds: Make rds selftests TAP compliant Allison Henderson
2026-05-06  2: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=177803463154.2357425.4119848919465141274.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