[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200610154923.27510-2-mcgrof@kernel.org>
Date: Wed, 10 Jun 2020 15:49:19 +0000
From: "Luis R. Rodriguez" <mcgrof@...nel.org>
To: gregkh@...uxfoundation.org, viro@...iv.linux.org.uk,
philipp.reisner@...bit.com, lars.ellenberg@...bit.com,
axboe@...nel.dk, bfields@...ldses.org, chuck.lever@...cle.com,
roopa@...ulusnetworks.com, nikolay@...ulusnetworks.com,
davem@...emloft.net, kuba@...nel.org, dhowells@...hat.com,
jarkko.sakkinen@...ux.intel.com, jmorris@...ei.org,
serge@...lyn.com, christian.brauner@...ntu.com
Cc: slyfox@...too.org, ast@...nel.org, keescook@...omium.org,
josh@...htriplett.org, ravenexp@...il.com, chainsaw@...too.org,
linux-fsdevel@...r.kernel.org, linux-nfs@...r.kernel.org,
bridge@...ts.linux-foundation.org, keyrings@...r.kernel.org,
linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org, Tiezhu Yang <yangtiezhu@...ngson.cn>,
Luis Chamberlain <mcgrof@...nel.org>
Subject: [PATCH 1/5] selftests: kmod: Use variable NAME in kmod_test_0001()
From: Tiezhu Yang <yangtiezhu@...ngson.cn>
Use the variable NAME instead of "\000" directly in kmod_test_0001().
Acked-by: Luis Chamberlain <mcgrof@...nel.org>
Signed-off-by: Tiezhu Yang <yangtiezhu@...ngson.cn>
Signed-off-by: Luis Chamberlain <mcgrof@...nel.org>
---
tools/testing/selftests/kmod/kmod.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/testing/selftests/kmod/kmod.sh b/tools/testing/selftests/kmod/kmod.sh
index 3702dbcc90a7..da60c3bd4f23 100755
--- a/tools/testing/selftests/kmod/kmod.sh
+++ b/tools/testing/selftests/kmod/kmod.sh
@@ -341,7 +341,7 @@ kmod_test_0001_driver()
kmod_defaults_driver
config_num_threads 1
- printf '\000' >"$DIR"/config_test_driver
+ printf $NAME >"$DIR"/config_test_driver
config_trigger ${FUNCNAME[0]}
config_expect_result ${FUNCNAME[0]} MODULE_NOT_FOUND
}
@@ -352,7 +352,7 @@ kmod_test_0001_fs()
kmod_defaults_fs
config_num_threads 1
- printf '\000' >"$DIR"/config_test_fs
+ printf $NAME >"$DIR"/config_test_fs
config_trigger ${FUNCNAME[0]}
config_expect_result ${FUNCNAME[0]} -EINVAL
}
--
2.26.2
Powered by blists - more mailing lists