From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, Namhyung Kim <namhyung@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: [PATCH 2/7] tools lib traceevent: Fix build failure on 32-bit arch
Date: Mon, 27 Apr 2015 14:04:04 -0300 [thread overview]
Message-ID: <1430154249-28268-3-git-send-email-acme@kernel.org> (raw)
In-Reply-To: <1430154249-28268-1-git-send-email-acme@kernel.org>
From: Namhyung Kim <namhyung@kernel.org>
In my i386 build, it failed like this:
CC event-parse.o
event-parse.c: In function 'print_str_arg':
event-parse.c:3868:5: warning: format '%lu' expects argument of type 'long unsigned int',
but argument 3 has type 'uint64_t' [-Wformat]
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
Acked-by: Javi Merino <javi.merino@arm.com>
Link: http://lkml.kernel.org/r/20150424020218.GF1905@sejong
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
tools/lib/traceevent/event-parse.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/lib/traceevent/event-parse.c b/tools/lib/traceevent/event-parse.c
index 12a7e2a40c89..aa21bd55bd8a 100644
--- a/tools/lib/traceevent/event-parse.c
+++ b/tools/lib/traceevent/event-parse.c
@@ -3865,7 +3865,7 @@ static void print_str_arg(struct trace_seq *s, void *data, int size,
} else if (el_size == 4) {
trace_seq_printf(s, "%u", *(uint32_t *)num);
} else if (el_size == 8) {
- trace_seq_printf(s, "%lu", *(uint64_t *)num);
+ trace_seq_printf(s, "%"PRIu64, *(uint64_t *)num);
} else {
trace_seq_printf(s, "BAD SIZE:%d 0x%x",
el_size, *(uint8_t *)num);
--
1.9.3
next prev parent reply other threads:[~2015-04-27 17:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 17:04 [GIT PULL 0/7] perf/urgent fixes Arnaldo Carvalho de Melo
2015-04-27 17:04 ` [PATCH 1/7] perf kmem: Fix compiles on RHEL6/OL6 Arnaldo Carvalho de Melo
2015-04-27 17:04 ` Arnaldo Carvalho de Melo [this message]
2015-04-27 17:04 ` [PATCH 3/7] perf top: Fix a segfault when kernel map is restricted Arnaldo Carvalho de Melo
2015-04-27 17:04 ` [PATCH 4/7] perf probe: Fix bug with global variables handling Arnaldo Carvalho de Melo
2015-04-27 17:04 ` [PATCH 5/7] perf bench futex: Fix hung wakeup tasks after requeueing Arnaldo Carvalho de Melo
2015-04-27 17:04 ` [PATCH 6/7] perf bench numa: Fixes of --quiet argument Arnaldo Carvalho de Melo
2015-04-27 17:04 ` [PATCH 7/7] perf bench numa: Fix immediate meeting of convergence condition Arnaldo Carvalho de Melo
2015-05-01 6:32 ` [GIT PULL 0/7] perf/urgent fixes Ingo Molnar
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=1430154249-28268-3-git-send-email-acme@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@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
Powered by JetHome