From: Jakub Kicinski <kuba@kernel.org>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org,
linux-kselftest@vger.kernel.org, shuah@kernel.org,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net-next v7 0/3] selftests: drv-net: convert so_txtime to drv-net
Date: Sun, 10 May 2026 17:42:19 -0700 [thread overview]
Message-ID: <20260510174219.74aeee6d@kernel.org> (raw)
In-Reply-To: <20260504174056.565319-1-willemdebruijn.kernel@gmail.com>
On Mon, 4 May 2026 13:38:31 -0400 Willem de Bruijn wrote:
> From: Willem de Bruijn <willemb@google.com>
>
> In preparation for extending to pacing hardware offload, convert the
> so_txtime.sh test to a drv-net test that can be run against netdevsim
> and real hardware.
>
> Two preparatory patches
> 1. support negative tests, where tests are expected to fail
> 2. add a tc helper
>
> See individual patches for details and detailed changelog
Hi Willem! Looks like we have some flakiness here:
https://netdev.bots.linux.dev/contest.html?executor=vmksft-net-drv-dbg&test=so-txtime-py
next prev parent reply other threads:[~2026-05-11 0:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 17:38 [PATCH net-next v7 0/3] selftests: drv-net: convert so_txtime to drv-net Willem de Bruijn
2026-05-04 17:38 ` [PATCH net-next v7 1/3] selftests: net: py: support cmd verifying expected failure Willem de Bruijn
2026-05-04 17:38 ` [PATCH net-next v7 2/3] selftests: net: py: add tc utility Willem de Bruijn
2026-05-04 17:38 ` [PATCH net-next v7 3/3] selftests: drv-net: convert so_txtime to drv-net Willem de Bruijn
2026-05-06 1:20 ` [PATCH net-next v7 0/3] " patchwork-bot+netdevbpf
2026-05-11 0:42 ` Jakub Kicinski [this message]
2026-05-11 3:43 ` Willem de Bruijn
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=20260510174219.74aeee6d@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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 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.