From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Will Deacon <will.deacon@arm.com>
Cc: linux-kernel@vger.kernel.org, Namhyung Kim <namhyung@kernel.org>,
David Ahern <dsahern@gmail.com>, Jiri Olsa <jolsa@redhat.com>,
Joonsoo Kim <js1304@gmail.com>, Minchan Kim <minchan@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [PATCH] tools: perf: consistently use PRIu64 for printing u64 values
Date: Thu, 23 Apr 2015 10:45:41 -0300 [thread overview]
Message-ID: <20150423134541.GC14773@redhat.com> (raw)
In-Reply-To: <1429796437-1790-1-git-send-email-will.deacon@arm.com>
Em Thu, Apr 23, 2015 at 02:40:37PM +0100, Will Deacon escreveu:
> Building the perf tool for 32-bit ARM results in the following build
> error due to a combination of an incorrect conversion specifier and
> compiling with -Werror:
>
> builtin-kmem.c: In function ‘print_page_summary’:
> builtin-kmem.c:644:9: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘u64’ [-Werror=format=]
> nr_alloc_freed, (total_alloc_freed_bytes) / 1024);
> ^
> builtin-kmem.c:647:9: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘u64’ [-Werror=format=]
> (total_page_alloc_bytes - total_alloc_freed_bytes) / 1024);
> ^
> cc1: all warnings being treated as errors
>
> This patch fixes the problem by consistently using PRIu64 for printing
> out u64 values.
Thanks, applied to perf/urgent.
- Arnaldo
next prev parent reply other threads:[~2015-04-23 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 13:40 [PATCH] tools: perf: consistently use PRIu64 for printing u64 values Will Deacon
2015-04-23 13:45 ` Arnaldo Carvalho de Melo [this message]
2015-05-01 10:13 ` [tip:perf/urgent] perf kmem: Consistently " tip-bot for Will Deacon
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=20150423134541.GC14773@redhat.com \
--to=acme@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=jolsa@redhat.com \
--cc=js1304@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=namhyung@kernel.org \
--cc=will.deacon@arm.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