We are not only checking if those options are correctly parsed from
kcmdline, but if in fact they are being passed to the final
(f)init_module call. This is why we use 'modprobe --show-depends'
instead of the simpler 'modprobe -c'.
---
testsuite/test-modprobe.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/testsuite/test-modprobe.c b/testsuite/test-modprobe.c
index 492b4d8..b5eaba3 100644
--- a/testsuite/test-modprobe.c
+++ b/testsuite/test-modprobe.c
@@ -176,7 +176,7 @@ static noreturn int modprobe_param_kcmdline(const struct
test *t)
exit(EXIT_FAILURE);
}
static DEFINE_TEST(modprobe_param_kcmdline,
- .description = "check if params are parsed correctly from kcmdline",
+ .description = "check if params from kcmdline are passed in fact passed
to (f)init_module call",
.config = {
[TC_UNAME_R] = "4.4.4",
[TC_ROOTFS] = TESTSUITE_ROOTFS
"test-modprobe/module-param-kcmdline",
--
1.9.0
--
To unsubscribe from this list: send the line "unsubscribe linux-modules" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
