public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Jean Delvare <khali@linux-fr•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Wolfram Sang <w.sang@pengutronix•de>
Subject: Re: linux-next: i2c tree build warning
Date: Thu, 26 Nov 2009 09:18:29 +0100	[thread overview]
Message-ID: <20091126091829.74d3b7ce@hyperion.delvare> (raw)
In-Reply-To: <20091126140600.2f55ab0e.sfr@canb.auug.org.au>

Hi Stephen,

On Thu, 26 Nov 2009 14:06:00 +1100, Stephen Rothwell wrote:
> 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").

Thanks for reporting. The warning did not show on my 32-bit x86 system,
and I guess it did not show on Wolfram's system either, otherwise we'd
have fixed it.

Does the following patch fix the warning for you?

--- linux-2.6.32-rc8.orig/drivers/misc/eeprom/at24.c	2009-11-26 09:14:45.000000000 +0100
+++ linux-2.6.32-rc8/drivers/misc/eeprom/at24.c	2009-11-26 09:14:15.000000000 +0100
@@ -227,7 +227,7 @@ static ssize_t at24_eeprom_read(struct a
 			if (status == 2)
 				status = count;
 		}
-		dev_dbg(&client->dev, "read %zu@%d --> %zd (%ld)\n",
+		dev_dbg(&client->dev, "read %zu@%d --> %d (%ld)\n",
 				count, offset, status, jiffies);
 
 		if (status == count)

If it does then I'll merge this into Wolfram's patch.

Thanks,
-- 
Jean Delvare

next prev parent reply	other threads:[~2009-11-26  8:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-26  3:06 linux-next: i2c tree build warning Stephen Rothwell
2009-11-26  8:18 ` Jean Delvare [this message]
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=20091126091829.74d3b7ce@hyperion.delvare \
    --to=khali@linux-fr$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=w.sang@pengutronix$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox