On Wed, Aug 17, 2022 at 12:49 PM 'Joe Fradley' via KUnit Development <kunit-dev@xxxxxxxxxxxxxxxx> wrote: > > Because KUnit test execution is not a guarantee with the kunit.enable > parameter we want to be careful to only taint the kernel only if an > actual test runs. 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@xxxxxxxxxx> Reviewed-by: Brendan Higgins <brendanhiggins@xxxxxxxxxx>
