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 v1 1/2] cyclictest: Fix printf format specifier
Date: Fri, 19 Feb 2021 17:33:39 +0100 [thread overview]
Message-ID: <20210219163340.6290-2-dwagner@suse.de> (raw)
In-Reply-To: <20210219163340.6290-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/cyclictest/cyclictest.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/src/cyclictest/cyclictest.c b/src/cyclictest/cyclictest.c
index c3d45f3ae31b..da502d426a8c 100644
--- a/src/cyclictest/cyclictest.c
+++ b/src/cyclictest/cyclictest.c
@@ -1732,15 +1732,15 @@ static void write_stats(FILE *f, void *data)
if (s->hist_array[j] == 0)
continue;
fprintf(f, "%s", comma ? ",\n" : "\n");
- fprintf(f, " \"%u\": %" PRIu64, j, s->hist_array[j]);
+ fprintf(f, " \"%u\": %ld", j, s->hist_array[j]);
comma = 1;
}
if (comma)
fprintf(f, "\n");
fprintf(f, " },\n");
- 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[i]->cpu);
fprintf(f, " \"node\": %d\n", par[i]->node);
--
2.30.0
next prev parent reply other threads:[~2021-02-19 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 16:33 [PATCH rt-tests v1 0/2] Fix printf format specifier Daniel Wagner
2021-02-19 16:33 ` Daniel Wagner [this message]
2021-03-03 23:29 ` [PATCH rt-tests v1 1/2] cyclictest: " John Kacur
2021-02-19 16:33 ` [PATCH rt-tests v1 2/2] cyclicdeadline.c: " Daniel Wagner
2021-03-03 23:29 ` 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=20210219163340.6290-2-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox