From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jean Delvare <khali@linux-fr.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Wolfram Sang <w.sang@pengutronix.de>
Subject: linux-next: i2c tree build warning
Date: Thu, 26 Nov 2009 14:06:00 +1100 [thread overview]
Message-ID: <20091126140600.2f55ab0e.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 471 bytes --]
Hi Jean,
Today's linux-next build (x86_64 allmodconfig) produced this warning:
drivers/misc/eeprom/at24.c: In function 'at24_eeprom_read':
drivers/misc/eeprom/at24.c:230: warning: format '%zd' expects type 'signed size_t', but argument 6 has type 'int'
Introduced by commit 39bfab2519e6f148f2508d719f9fc5f4581aeefd ("at24: Use
timeout also for read").
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2009-11-26 3:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 3:06 Stephen Rothwell [this message]
2009-11-26 8:18 ` linux-next: i2c tree build warning Jean Delvare
2009-11-26 8:50 ` Stephen Rothwell
2009-11-26 10:50 ` Wolfram Sang
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=20091126140600.2f55ab0e.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=w.sang@pengutronix.de \
/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