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, ncardwell@google.com, shuah@kernel.org,
linux-kselftest@vger.kernel.org, fw@strlen.de,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net-next v2 0/2] selftests/net: add packetdrill
Date: Tue, 10 Sep 2024 15:26:40 -0700 [thread overview]
Message-ID: <20240910152640.429920be@kernel.org> (raw)
In-Reply-To: <66e085c5c2627_c43f1294df@willemb.c.googlers.com.notmuch>
On Tue, 10 Sep 2024 13:45:41 -0400 Willem de Bruijn wrote:
> Which literally just inserting uname -n into the two invocations,
> right?
Yes, AFAIU.
> I can send that. And then also add some CONFIGs we discussed:
SG!
> And in the same series another two packetdrill testsuites, around 20
> tests, say.
SG!
next prev parent reply other threads:[~2024-09-10 22:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 23:15 [PATCH net-next v2 0/2] selftests/net: add packetdrill Willem de Bruijn
2024-09-05 23:15 ` [PATCH net-next v2 1/2] selftests: support interpreted scripts with ksft_runner.sh Willem de Bruijn
2024-09-05 23:15 ` [PATCH net-next v2 2/2] selftests/net: integrate packetdrill with ksft Willem de Bruijn
2024-09-06 11:43 ` Matthieu Baerts
2024-09-06 15:36 ` Willem de Bruijn
2024-09-06 16:26 ` Matthieu Baerts
2024-09-06 23:28 ` Willem de Bruijn
2024-09-07 0:04 ` Jakub Kicinski
2024-09-09 7:42 ` Matthieu Baerts
2024-09-09 13:15 ` Willem de Bruijn
2024-09-09 14:14 ` Matthieu Baerts
2024-09-09 17:21 ` [PATCH net-next v2 0/2] selftests/net: add packetdrill Jakub Kicinski
2024-09-10 17:45 ` Willem de Bruijn
2024-09-10 22:26 ` Jakub Kicinski [this message]
2024-09-10 0:40 ` 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=20240910152640.429920be@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=linux-kselftest@vger.kernel.org \
--cc=ncardwell@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).