From: Jakub Kicinski <kuba@kernel.org>
To: Karl Mehltretter <kmehltretter@gmail.com>
Cc: Jeremy Kerr <jk@codeconstruct.com.au>,
Matt Johnston <matt@codeconstruct.com.au>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, Geert Uytterhoeven <geert@linux-m68k.org>,
Brendan Higgins <brendan.higgins@linux.dev>,
David Gow <david@davidgow.net>, Rae Moar <raemoar63@gmail.com>,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3] net: mctp: Make flow KUnit coverage an explicit opt-in
Date: Wed, 7 Oct 2026 19:11:57 -0700 [thread overview]
Message-ID: <20261007191157.0fd327ba@kernel.org> (raw)
In-Reply-To: <20261002212058.25117-1-kmehltretter@gmail.com>
On Fri, 2 Oct 2026 23:20:58 +0200 Karl Mehltretter wrote:
> MCTP_TEST selects MCTP_FLOWS, so KUNIT_ALL_TESTS builds flow support and
> SKB_EXTENSIONS even when no transport needs them. KUnit's style guide
> says tests should not select otherwise unused functionality. The CRC
> and crypto library tests use explicit ENABLE_ALL_FOR_KUNIT options for
> full coverage.
>
> Remove the selection from MCTP_TEST. The core suite remains available
> without flows; its two flow cases use their existing skip paths. Add
> MCTP_ENABLE_ALL_FOR_KUNIT to opt into full coverage, and enable it in
> all_tests.config and a dedicated net/mctp/.kunitconfig. Both profiles
> run the flow cases without a hardware transport.
>
> A plain MCTP_TEST=y configuration without the opt-in now skips those
> two cases. This is the coverage cost of leaving otherwise unused flow
> support disabled.
>
> Assisted-by: LLM
> Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
> ---
> Changes in v3:
> - Keep the core suite available without MCTP_FLOWS; a plain MCTP_TEST=y
> configuration now skips only the two flow cases.
> - Add MCTP_ENABLE_ALL_FOR_KUNIT to retain full coverage in
> all_tests.config and a focused net/mctp/.kunitconfig.
> - Drop the Fixes tag because this changes test configuration rather
> than fixing a runtime MCTP bug.
>
> v2: https://lore.kernel.org/r/20260928205352.30502-1-kmehltretter@gmail.com/
> v1: https://lore.kernel.org/r/20260925192510.93840-1-kmehltretter@gmail.com/
>
> Validation: The MCTP KUnit suites were built with GCC 15.2 and booted
> under QEMU 10.2.1 on an isolated source export from net-next
> 014d795c7383, with the changed Kconfig files copied from 071876fd5048.
> Without the opt-in, mctp-sock passed 5/5 tests and mctp-route passed
> 21/23 tests with two expected flow-case skips. With the opt-in, both
> suites passed all 5 and 23 tests, respectively. On the full
> 071876fd5048 tree, the new net/mctp/.kunitconfig resolves all requested
> symbols and selects MCTP_FLOWS and SKB_EXTENSIONS.
I don't think this is worth applying
--
pw-bot: reject
prev parent reply other threads:[~2026-10-08 2:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 21:20 [PATCH net-next v3] net: mctp: Make flow KUnit coverage an explicit opt-in Karl Mehltretter
2026-10-08 2:11 ` Jakub Kicinski [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=20261007191157.0fd327ba@kernel.org \
--to=kuba@kernel.org \
--cc=brendan.higgins@linux.dev \
--cc=davem@davemloft.net \
--cc=david@davidgow.net \
--cc=edumazet@google.com \
--cc=geert@linux-m68k.org \
--cc=horms@kernel.org \
--cc=jk@codeconstruct.com.au \
--cc=kmehltretter@gmail.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=raemoar63@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