From: Daniel Wagner <dwagner@suse.de>
To: Clark Williams <williams@redhat.com>, John Kacur <jkacur@redhat.com>
Cc: linux-rt-users@vger.kernel.org, Daniel Wagner <dwagner@suse.de>
Subject: [PATCH rt-tests v2 2/3] signaltest: Fix printf format specifier
Date: Thu, 8 Jul 2021 17:18:26 +0200 [thread overview]
Message-ID: <20210708151827.21430-3-dwagner@suse.de> (raw)
In-Reply-To: <20210708151827.21430-1-dwagner@suse.de>
The fields are not uint64 just longs, update the printf format
specifiers.
Signed-off-by: Daniel Wagner <dwagner@suse.de>
---
src/signaltest/signaltest.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/signaltest/signaltest.c b/src/signaltest/signaltest.c
index 6e8f6b51b003..4d89a1aba9d9 100644
--- a/src/signaltest/signaltest.c
+++ b/src/signaltest/signaltest.c
@@ -393,9 +393,9 @@ static void write_stats(FILE *f, void *data)
for (i = 0; i < num_threads; i++) {
fprintf(f, " \"%u\": {\n", i);
s = &par->stats[i];
- fprintf(f, " \"cycles\": %" PRIu64 ",\n", s->cycles);
- fprintf(f, " \"min\": %" PRIu64 ",\n", s->min);
- fprintf(f, " \"max\": %" PRIu64 ",\n", s->max);
+ fprintf(f, " \"cycles\": %ld,\n", s->cycles);
+ fprintf(f, " \"min\": %ld,\n", s->min);
+ fprintf(f, " \"max\": %ld,\n", s->max);
fprintf(f, " \"avg\": %.2f,\n", s->avg/s->cycles);
fprintf(f, " \"cpu\": %d\n", par->cpu);
fprintf(f, " }%s\n", i == num_threads - 1 ? "" : ",");
--
2.32.0
next prev parent reply other threads:[~2021-07-08 15:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 15:18 [PATCH rt-tests v2 0/3] Fix a few fallouts Daniel Wagner
2021-07-08 15:18 ` [PATCH rt-tests v2 1/3] rt-numa: Use sched_getaffinity() instead of pthread_getaffinity_np() Daniel Wagner
2021-07-09 17:58 ` John Kacur
2021-07-19 8:00 ` Daniel Wagner
2021-07-08 15:18 ` Daniel Wagner [this message]
2021-07-08 15:18 ` [PATCH rt-tests v2 3/3] cyclicdeadline: Fix buffer allocation Daniel Wagner
2021-07-09 18:01 ` John Kacur
2021-07-19 8:05 ` Daniel Wagner
2021-07-09 18:02 ` John Kacur
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=20210708151827.21430-3-dwagner@suse.de \
--to=dwagner@suse.de \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.