aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/of/unittest.c
diff options
context:
space:
mode:
authorFrank Rowand <frank.rowand@sony.com>2022-02-10 17:08:19 -0600
committerRob Herring <robh@kernel.org>2022-02-15 13:59:35 -0600
commit54eb8dc8f338962e12760fb718f4ca39a8cf3aa9 (patch)
tree864bcc7e565078ef67e385c8f86b1be45500a4f1 /drivers/of/unittest.c
parentdt-bindings: timer: armv7m-systick: convert to dtschema (diff)
downloadlinux-dev-54eb8dc8f338962e12760fb718f4ca39a8cf3aa9.tar.xz
linux-dev-54eb8dc8f338962e12760fb718f4ca39a8cf3aa9.zip
of: unittest: print pass messages at PR_INFO level
Printing the devicetree unittest pass message for each passed test creates much console verbosity. The existing pass messages are printed at loglevel KERN_DEBUG so they will not print by default. Change default to print the pass messages at loglevel PR_INFO so they will print with the default console loglevel. The test community expects either a pass or a fail message for each test in a test suite. The messages are typically post-processed to report pass/fail results. Signed-off-by: Frank Rowand <frank.rowand@sony.com> Tested-by: Linux Kernel Functional Testing <lkft@linaro.org> Signed-off-by: Rob Herring <robh@kernel.org> Link: https://lore.kernel.org/r/20220210230819.3303212-1-frowand.list@gmail.com
Diffstat (limited to 'drivers/of/unittest.c')
-rw-r--r--drivers/of/unittest.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/of/unittest.c b/drivers/of/unittest.c
index 70992103c07d..9012e6900965 100644
--- a/drivers/of/unittest.c
+++ b/drivers/of/unittest.c
@@ -44,7 +44,7 @@ static struct unittest_results {
pr_err("FAIL %s():%i " fmt, __func__, __LINE__, ##__VA_ARGS__); \
} else { \
unittest_results.passed++; \
- pr_debug("pass %s():%i\n", __func__, __LINE__); \
+ pr_info("pass %s():%i\n", __func__, __LINE__); \
} \
failed; \
})