Documentation: kunit: Test Kconfig entries shouldn't select other configs

Add a note to the Kconfig section of style.rst to use 'depends on' rather
than 'selects' for dependencies, as this can cause users of
CONFIG_KUNIT_ALL_TESTS to suddenly grow unexpected dependencies.

Link: https://lore.kernel.org/r/20260627082921.1709181-1-david@davidgow.net
Signed-off-by: David Gow <david@davidgow.net>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
This commit is contained in:
David Gow
2026-06-27 16:29:19 +08:00
committed by Shuah Khan
parent 643ec8ff7d
commit 7eac333051

View File

@@ -164,9 +164,10 @@ This Kconfig entry must:
* be visible only if ``CONFIG_KUNIT_ALL_TESTS`` is not enabled.
* have a default value of ``CONFIG_KUNIT_ALL_TESTS``.
* have a brief description of KUnit in the help text.
If we are not able to meet above conditions (for example, the test is unable to
be built as a module), Kconfig entries for tests should be tristate.
* depend on the feature being tested, rather than selecting it (so that
enabling ``CONFIG_KUNIT_ALL_TESTS`` does not enable unrelated functionality).
* be ``tristate``, unless there is a specific reason that the test cannot be
built as a module.
For example, a Kconfig entry might look like: