[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241216201148.535115-3-briannorris@chromium.org>
Date: Mon, 16 Dec 2024 12:11:43 -0800
From: Brian Norris <briannorris@...omium.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Maxime Ripard <mripard@...nel.org>,
linux-acpi@...r.kernel.org,
Rae Moar <rmoar@...gle.com>,
Rob Herring <robh@...nel.org>,
David Gow <davidgow@...gle.com>,
linux-kselftest@...r.kernel.org,
"Rafael J. Wysocki" <rafael@...nel.org>,
kunit-dev@...glegroups.com,
linux-kernel@...r.kernel.org,
Brian Norris <briannorris@...omium.org>
Subject: [PATCH v3 2/3] drivers: base: test: Enable device model tests with KUNIT_ALL_TESTS
Per commit bebe94b53eb7 ("drivers: base: default KUNIT_* fragments to
KUNIT_ALL_TESTS"), it seems like we should default to KUNIT_ALL_TESTS.
This enables these platform_device tests for common configurations, such
as with:
./tools/testing/kunit/kunit.py run
Signed-off-by: Brian Norris <briannorris@...omium.org>
---
(no changes since v1)
drivers/base/test/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/base/test/Kconfig b/drivers/base/test/Kconfig
index 5c7fac80611c..2756870615cc 100644
--- a/drivers/base/test/Kconfig
+++ b/drivers/base/test/Kconfig
@@ -12,6 +12,7 @@ config TEST_ASYNC_DRIVER_PROBE
config DM_KUNIT_TEST
tristate "KUnit Tests for the device model" if !KUNIT_ALL_TESTS
depends on KUNIT
+ default KUNIT_ALL_TESTS
config DRIVER_PE_KUNIT_TEST
tristate "KUnit Tests for property entry API" if !KUNIT_ALL_TESTS
--
2.47.1.613.gc27f4b7a9f-goog
Powered by blists - more mailing lists