From: Jakub Kicinski <kuba@kernel.org>
To: Allison Henderson <achender@kernel.org>
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
pabeni@redhat.com, edumazet@google.com, rds-devel@oss.oracle.com,
horms@kernel.org, linux-rdma@vger.kernel.org,
allison.henderson@oracle.com
Subject: Re: [PATCH net-next v1 0/3] selftests: rds: ksft cleanups
Date: Tue, 10 Mar 2026 18:53:05 -0700 [thread overview]
Message-ID: <20260310185305.017976e4@kernel.org> (raw)
In-Reply-To: <20260308055835.1338257-1-achender@kernel.org>
On Sat, 7 Mar 2026 22:58:32 -0700 Allison Henderson wrote:
> This set addresses a few rds selftests clean ups and bugs encountered
> when running in the ksft framework. The first patch is a clean up
> patch that addresses pylint warnings, but otherwise no functional
> changes. The next patch moves the test time out to a ksft settings
> file so that the time out is set appropriately. And lastly we fix a
> tcpdump segfault caused by deprecated a os.fork() call.
Looks good! So this is enough to make ksft work? Or just the first
batch of obvious fixes? :)
next prev parent reply other threads:[~2026-03-11 1:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-08 5:58 [PATCH net-next v1 0/3] selftests: rds: ksft cleanups Allison Henderson
2026-03-08 5:58 ` [PATCH net-next v1 1/3] selftests: rds: Fix pylint warnings Allison Henderson
2026-03-08 5:58 ` [PATCH net-next v1 2/3] selftests: rds: Add ksft timeout Allison Henderson
2026-03-08 5:58 ` [PATCH net-next v1 3/3] selftests: rds: Fix tcpdump segfault in rds selftests Allison Henderson
2026-03-11 1:53 ` Jakub Kicinski [this message]
2026-03-11 4:56 ` [PATCH net-next v1 0/3] selftests: rds: ksft cleanups Allison Henderson
2026-03-12 0:05 ` Jakub Kicinski
2026-03-16 0:55 ` Jakub Kicinski
2026-03-11 2:00 ` patchwork-bot+netdevbpf
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=20260310185305.017976e4@kernel.org \
--to=kuba@kernel.org \
--cc=achender@kernel.org \
--cc=allison.henderson@oracle.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rds-devel@oss.oracle.com \
/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