From: Jakub Kicinski <kuba@kernel.org>
To: Peter Lee <fronce09@gmail.com>
Cc: netdev@vger.kernel.org, dsahern@kernel.org, idosch@nvidia.com,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
horms@kernel.org
Subject: Re: [RFC] net: ipv4: add KUnit coverage for net/ipv4*
Date: Sat, 2 May 2026 09:51:08 -0700 [thread overview]
Message-ID: <20260502095108.752a12bf@kernel.org> (raw)
In-Reply-To: <CA+2kspPQ0ZyirDsCyDugzb7Wtt9MPNPdz2xDaxM4DGh+hqy=XA@mail.gmail.com>
On Sat, 2 May 2026 23:08:38 +1000 Peter Lee wrote:
> Was looking to start contributing to the kernel and thought i would start
> with some test coverage action. For net/ipv4, are you looking to increase
> the level of kunit testing across this submodule, or do you prefer coverage
> only through higher-level selftests?
What's your methodology? If you're planning to generate some code with
AI we are not interested.
parent reply other threads:[~2026-05-02 16:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CA+2kspPQ0ZyirDsCyDugzb7Wtt9MPNPdz2xDaxM4DGh+hqy=XA@mail.gmail.com>]
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=20260502095108.752a12bf@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fronce09@gmail.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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