From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: build warnings after merge of the regmap tree
Date: Tue, 9 Aug 2011 13:21:11 +1000 [thread overview]
Message-ID: <20110809132111.af88776afc00f9e87e1bd6a1@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]
Hi Mark,
After merging the regmap tree, today's linux-next build (x86_64
allmodconfig) produced these warning:
drivers/base/regmap/regmap-debugfs.c: In function 'regmap_map_read_file':
drivers/base/regmap/regmap-debugfs.c:71:6: warning: field precision should have type 'int', but argument 4 has type 'size_t'
drivers/base/regmap/regmap-debugfs.c:78:7: warning: field precision should have type 'int', but argument 4 has type 'size_t'
Introduced by commit 31244e396fa9 ("regmap: Provide register map dump via
debugfs").
In file included from include/trace/ftrace.h:296:0,
from include/trace/define_trace.h:96,
from include/trace/events/regmap.h:112,
from drivers/base/regmap/regmap.c:19:
include/trace/events/regmap.h: In function 'ftrace_raw_output_regmap_block':
include/trace/events/regmap.h:58:1: warning: format '%d' expects type 'int', but argument 5 has type 'size_t'
Introduced by commit fb2736bbaee0 ("regmap: Add basic tracepoints").
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2011-08-09 3:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 3:21 Stephen Rothwell [this message]
2011-08-09 15:01 ` linux-next: build warnings after merge of the regmap tree Mark Brown
2013-03-27 4:47 Stephen Rothwell
2013-03-27 10:24 ` Mark Brown
2013-03-27 10:35 ` Stephen Rothwell
2015-07-17 4:39 Stephen Rothwell
2015-07-17 9:44 ` Nariman Poushin
2015-07-17 10:34 ` Mark Brown
2015-07-17 15:29 ` Nariman Poushin
2015-07-17 16:45 ` Charles Keepax
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=20110809132111.af88776afc00f9e87e1bd6a1@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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;
as well as URLs for NNTP newsgroup(s).