summaryrefslogtreecommitdiff
path: root/include/kunit
diff options
context:
space:
mode:
authorJoe Fradley <joefradley@google.com>2022-08-23 07:24:55 -0700
committerShuah Khan <skhan@linuxfoundation.org>2022-09-30 13:17:49 -0600
commit7d97635b72813d80f909ad24d7a64b2fe9a29c0b (patch)
treea3b4ec2ad2e3e288507a6b3948dd24a6761ce79f /include/kunit
parentd20a6ba5e3be5f8d9002c6c5a5d4dfecc5dc48f9 (diff)
downloadlinux-next-7d97635b72813d80f909ad24d7a64b2fe9a29c0b.tar.gz
kunit: no longer call module_info(test, "Y") for kunit modules
Because KUnit test execution is not a guarantee with the kunit.enable parameter we want to be careful to only taint the kernel when actual tests run. Calling module_info(test, "Y") for every KUnit module automatically causes the kernel to be tainted upon module load. Therefore, we're removing this call and relying on the KUnit framework to taint the kernel or not. Signed-off-by: Joe Fradley <joefradley@google.com> Reviewed-by: David Gow <davidgow@google.com> Reviewed-by: Brendan Higgins <brendanhiggins@google.com> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
Diffstat (limited to 'include/kunit')
-rw-r--r--include/kunit/test.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/include/kunit/test.h b/include/kunit/test.h
index a6d6892b7957..20cc4770cb3f 100644
--- a/include/kunit/test.h
+++ b/include/kunit/test.h
@@ -253,7 +253,6 @@ static inline int kunit_run_all_tests(void)
#endif /* IS_BUILTIN(CONFIG_KUNIT) */
#define __kunit_test_suites(unique_array, ...) \
- MODULE_INFO(test, "Y"); \
static struct kunit_suite *unique_array[] \
__aligned(sizeof(struct kunit_suite *)) \
__used __section(".kunit_test_suites") = { __VA_ARGS__ }