Linux-EROFS Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Collingbourne via Linux-erofs <linux-erofs@lists.ozlabs.org>
To: xiang@kernel.org
Cc: Peter Collingbourne <pcc@google.com>, linux-erofs@lists.ozlabs.org
Subject: [PATCH] erofs-utils: Print configuration only at INFO debug level
Date: Tue,  8 Feb 2022 16:53:06 -0800	[thread overview]
Message-ID: <20220209005307.1288161-1-pcc@google.com> (raw)

The information printed by erofs_show_config is not useful for ordinary
users of the program, and it certainly doesn't count as a warning,
so let's only print it at the INFO debug level or greater.

Signed-off-by: Peter Collingbourne <pcc@google.com>
---
 lib/config.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/config.c b/lib/config.c
index 363dcc5..08deb6f 100644
--- a/lib/config.c
+++ b/lib/config.c
@@ -34,7 +34,7 @@ void erofs_show_config(void)
 {
 	const struct erofs_configure *c = &cfg;
 
-	if (c->c_dbg_lvl < EROFS_WARN)
+	if (c->c_dbg_lvl < EROFS_INFO)
 		return;
 	erofs_dump("\tc_version:           [%8s]\n", c->c_version);
 	erofs_dump("\tc_dbg_lvl:           [%8d]\n", c->c_dbg_lvl);
-- 
2.35.0.263.gb82422642f-goog


             reply	other threads:[~2022-02-09  0:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09  0:53 Peter Collingbourne via Linux-erofs [this message]
2022-02-09  0:53 ` [PATCH] erofs-utils: Print program name and version to stdout Peter Collingbourne via Linux-erofs
2022-02-09  1:48   ` Gao Xiang
2022-02-09  1:47 ` [PATCH] erofs-utils: Print configuration only at INFO debug level Gao Xiang

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=20220209005307.1288161-1-pcc@google.com \
    --to=linux-erofs@lists.ozlabs.org \
    --cc=pcc@google.com \
    --cc=xiang@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