From: Eric Biggers <ebiggers@kernel.org>
To: linux-ext4@vger.kernel.org
Subject: [PATCH 2/4] debugfs: fix a -Wformat warning in dump_journal()
Date: Sat, 28 Jan 2023 14:46:49 -0800 [thread overview]
Message-ID: <20230128224651.59593-3-ebiggers@kernel.org> (raw)
In-Reply-To: <20230128224651.59593-1-ebiggers@kernel.org>
From: Eric Biggers <ebiggers@google.com>
This really should just use PRIi64, but e2fsprogs doesn't use the
inttypes.h format specifiers elsewhere, so just be consistent for now.
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
debugfs/logdump.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/debugfs/logdump.c b/debugfs/logdump.c
index 036b50baf..938b48907 100644
--- a/debugfs/logdump.c
+++ b/debugfs/logdump.c
@@ -479,7 +479,8 @@ static void dump_journal(char *cmdname, FILE *out_file,
if ((blocknr == first_transaction_blocknr) &&
(cur_counts != 0) && dump_old && (dump_counts != -1)) {
- fprintf(out_file, "Dump all %lld journal records.\n", cur_counts);
+ fprintf(out_file, "Dump all %lld journal records.\n",
+ (long long)cur_counts);
break;
}
--
2.39.1
next prev parent reply other threads:[~2023-01-28 22:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 22:46 [PATCH 0/4] e2fsprogs: a few more warning fixes Eric Biggers
2023-01-28 22:46 ` [PATCH 1/4] ci.yml: ensure -Werror really gets used in all cases Eric Biggers
2023-01-30 5:07 ` Theodore Ts'o
2023-01-28 22:46 ` Eric Biggers [this message]
2023-01-30 5:08 ` [PATCH 2/4] debugfs: fix a -Wformat warning in dump_journal() Theodore Ts'o
2023-01-28 22:46 ` [PATCH 3/4] lib/ext2fs: don't warn about lack of getmntent on Windows Eric Biggers
2023-01-30 5:08 ` Theodore Ts'o
2023-01-28 22:46 ` [PATCH 4/4] lib/uuid: remove unneeded Windows UUID workaround Eric Biggers
2023-01-30 5:09 ` 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=20230128224651.59593-3-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--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).