From: Theodore Ts'o <tytso@mit.edu>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>
Cc: john.jolly@gmail.com, Theodore Ts'o <tytso@mit.edu>
Subject: [PATCH 2/4] mke2fs: don't display bigalloc/quota fs feature warnings in quiet mode
Date: Sun, 31 Mar 2013 20:44:01 -0400 [thread overview]
Message-ID: <1364777043-20610-3-git-send-email-tytso@mit.edu> (raw)
In-Reply-To: <1364777043-20610-1-git-send-email-tytso@mit.edu>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
---
misc/mke2fs.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/misc/mke2fs.c b/misc/mke2fs.c
index fe5ce7d..7448255 100644
--- a/misc/mke2fs.c
+++ b/misc/mke2fs.c
@@ -1942,13 +1942,15 @@ profile_error:
exit(1);
}
- if (fs_param.s_feature_ro_compat & EXT4_FEATURE_RO_COMPAT_BIGALLOC)
+ if (!quiet &&
+ (fs_param.s_feature_ro_compat & EXT4_FEATURE_RO_COMPAT_BIGALLOC))
fprintf(stderr, _("\nWarning: the bigalloc feature is still "
"under development\n"
"See https://ext4.wiki.kernel.org/"
"index.php/Bigalloc for more information\n\n"));
- if (fs_param.s_feature_ro_compat & EXT4_FEATURE_RO_COMPAT_QUOTA)
+ if (!quiet &&
+ (fs_param.s_feature_ro_compat & EXT4_FEATURE_RO_COMPAT_QUOTA))
fprintf(stderr, _("\nWarning: the quota feature is still "
"under development\n"
"See https://ext4.wiki.kernel.org/"
--
1.7.12.rc0.22.gcdd159b
next prev parent reply other threads:[~2013-04-01 0:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 3:44 Failure of resize2fs past 4TB John Jolly
2013-03-28 3:57 ` Eric Sandeen
2013-03-28 11:55 ` Theodore Ts'o
2013-04-01 0:43 ` [PATCH 0/4] e2fsprogs: fix off-line resizing of small ext4 file systems Theodore Ts'o
2013-04-01 0:44 ` [PATCH 1/4] resize2fs: fix off-line resize of file systems with flex_bg && !resize_inode Theodore Ts'o
2013-04-01 0:44 ` Theodore Ts'o [this message]
2013-04-01 0:44 ` [PATCH 3/4] tests: create crcsum progam to support resizing tests Theodore Ts'o
2013-04-01 0:44 ` [PATCH 4/4] tests: add more tests for off-line resizing Theodore Ts'o
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=1364777043-20610-3-git-send-email-tytso@mit.edu \
--to=tytso@mit.edu \
--cc=john.jolly@gmail.com \
--cc=linux-ext4@vger.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).