From: Mark Wielaard <mark@klomp.org>
To: debugedit@sourceware.org
Cc: Mark Wielaard <mark@klomp.org>
Subject: [PATCH] debugedit: Use 'z', not 'Z' as conversion specifier
Date: Sat, 25 Mar 2023 00:58:54 +0100 [thread overview]
Message-ID: <20230324235854.2335544-1-mark@klomp.org> (raw)
Both are valid for size_t but 'z' is the standard one.
Signed-off-by: Mark Wielaard <mark@klomp.org>
---
tools/debugedit.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/debugedit.c b/tools/debugedit.c
index b3422d7..3d75b8f 100644
--- a/tools/debugedit.c
+++ b/tools/debugedit.c
@@ -3185,7 +3185,7 @@ handle_build_id (DSO *dso, Elf_Data *build_id,
if (build_id_size != 16 && build_id_size != 20)
{
- error (1, 0, "Cannot handle %Zu-byte build ID", build_id_size);
+ error (1, 0, "Cannot handle %zu-byte build ID", build_id_size);
}
int i = -1;
--
2.31.1
next reply other threads:[~2023-03-24 23:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 23:58 Mark Wielaard [this message]
2023-04-21 12:40 ` Mark Wielaard
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=20230324235854.2335544-1-mark@klomp.org \
--to=mark@klomp.org \
--cc=debugedit@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).