From: frowand.list@gmail.com
To: Rob Herring <robh+dt@kernel.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
Brendan Higgins <brendanhiggins@google.com>,
Anders Roxell <anders.roxell@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/1] of: unittest: config option - print pass message at same level as fail
Date: Wed, 2 Feb 2022 13:45:13 -0600 [thread overview]
Message-ID: <20220202194513.2840070-1-frowand.list@gmail.com> (raw)
From: Frank Rowand <frank.rowand@sony.com>
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.
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.
The pass messages can currently be reported by enabling KERN_DEBUG
loglevel for the console, but this also results in other additional
messages. Create OF_UNITTEST_SHOW_PASS to enable printing the pass
messages at the same loglevel as the fail messages.
Signed-off-by: Frank Rowand <frank.rowand@sony.com>
---
drivers/of/Kconfig | 10 ++++++++++
drivers/of/unittest.c | 5 ++++-
2 files changed, 14 insertions(+), 1 deletion(-)
diff --git a/drivers/of/Kconfig b/drivers/of/Kconfig
index 80b5fd44ab1c..6ad05df4f7d4 100644
--- a/drivers/of/Kconfig
+++ b/drivers/of/Kconfig
@@ -25,6 +25,16 @@ config OF_UNITTEST
If unsure, say N here, but this option is safe to enable.
+config OF_UNITTEST_SHOW_PASS
+ bool "Device Tree runtime unit tests, report each pass"
+ depends on OF_UNITTEST
+ help
+ The messages reporting an individual test pass are normally
+ printed at loglevel KERN_DEBUG. Enable this option to print
+ the PASS messages at the same loglevel as the FAIL messages.
+
+ If unsure, say N here, but this option is safe to enable.
+
config OF_ALL_DTBS
bool "Build all Device Tree Blobs"
depends on COMPILE_TEST
diff --git a/drivers/of/unittest.c b/drivers/of/unittest.c
index 70992103c07d..efcec1c6c895 100644
--- a/drivers/of/unittest.c
+++ b/drivers/of/unittest.c
@@ -44,7 +44,10 @@ 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__); \
+ if (IS_ENABLED(CONFIG_OF_UNITTEST_SHOW_PASS)) \
+ pr_err("pass %s():%i\n", __func__, __LINE__); \
+ else \
+ pr_debug("pass %s():%i\n", __func__, __LINE__); \
} \
failed; \
})
--
Frank Rowand <frank.rowand@sony.com>
next reply other threads:[~2022-02-02 19:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 19:45 frowand.list [this message]
2022-02-03 21:23 ` [PATCH 1/1] of: unittest: config option - print pass message at same level as fail Frank Rowand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220202194513.2840070-1-frowand.list@gmail.com \
--to=frowand.list@gmail.com \
--cc=anders.roxell@linaro.org \
--cc=brendanhiggins@google.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).