[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200505102700.7912-1-anders.roxell@linaro.org>
Date: Tue, 5 May 2020 12:27:00 +0200
From: Anders Roxell <anders.roxell@...aro.org>
To: brendanhiggins@...gle.com
Cc: john.johansen@...onical.com, jmorris@...ei.org, serge@...lyn.com,
tytso@....edu, adilger.kernel@...ger.ca,
gregkh@...uxfoundation.org, akpm@...ux-foundation.org,
linux-kselftest@...r.kernel.org, kunit-dev@...glegroups.com,
linux-kernel@...r.kernel.org, linux-ext4@...r.kernel.org,
linux-security-module@...r.kernel.org, elver@...gle.com,
davidgow@...gle.com, Anders Roxell <anders.roxell@...aro.org>
Subject: [PATCH v2 1/6] kunit: Kconfig: enable a KUNIT_RUN_ALL fragment
Make it easier to enable all KUnit fragments. This is needed for kernel
test-systems, so its easy to get all KUnit tests enabled and if new gets
added they will be enabled as well. Fragments that has to be builtin
will be missed if CONFIG_KUNIT_RUN_ALL is set as a module.
Signed-off-by: Anders Roxell <anders.roxell@...aro.org>
---
lib/kunit/Kconfig | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/lib/kunit/Kconfig b/lib/kunit/Kconfig
index 95d12e3d6d95..537f37bc8400 100644
--- a/lib/kunit/Kconfig
+++ b/lib/kunit/Kconfig
@@ -41,4 +41,10 @@ config KUNIT_EXAMPLE_TEST
is intended for curious hackers who would like to understand how to
use KUnit for kernel development.
+config KUNIT_RUN_ALL
+ tristate "KUnit run all test"
+ help
+ Enables all KUnit tests, if they can be enabled.
+ That depends on if KUnit is enabled as a module or builtin.
+
endif # KUNIT
--
2.20.1
Powered by blists - more mailing lists