From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Sangwook Lee <sangwook.lee@linaro.org>,
Seok-Young Jang <quartz.jang@samsung.com>
Subject: [PATCH -next] media: fix i2c/s5k4ecgx printk format warning
Date: Tue, 16 Oct 2012 13:17:59 -0700 [thread overview]
Message-ID: <507DC0F7.207@xenotime.net> (raw)
In-Reply-To: <20121016145856.cfddc9c898c31b1c686804d7@canb.auug.org.au>
From: Randy Dunlap <rdunlap@xenotime.net>
Fix printk format warning for size_t variable:
drivers/media/i2c/s5k4ecgx.c:346:2: warning: format '%d' expects type 'int', but argument 4 has type 'size_t'
Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
Cc: Sangwook Lee <sangwook.lee@linaro.org>
Cc: Seok-Young Jang <quartz.jang@samsung.com>
---
drivers/media/i2c/s5k4ecgx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20121016.orig/drivers/media/i2c/s5k4ecgx.c
+++ linux-next-20121016/drivers/media/i2c/s5k4ecgx.c
@@ -343,7 +343,7 @@ static int s5k4ecgx_load_firmware(struct
}
regs_num = le32_to_cpu(get_unaligned_le32(fw->data));
- v4l2_dbg(3, debug, sd, "FW: %s size %d register sets %d\n",
+ v4l2_dbg(3, debug, sd, "FW: %s size %zu register sets %d\n",
S5K4ECGX_FIRMWARE, fw->size, regs_num);
regs_num++; /* Add header */
next prev parent reply other threads:[~2012-10-16 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 3:58 linux-next: Tree for Oct 16 Stephen Rothwell
2012-10-16 3:58 ` Stephen Rothwell
2012-10-16 20:05 ` linux-next: Tree for Oct 16 (readeon_legacy) Randy Dunlap
2012-10-16 22:44 ` Alex Deucher
2012-10-16 20:17 ` Randy Dunlap [this message]
2012-10-16 20:30 ` [PATCH -next] regmap: fix regmap.c printk format warning Randy Dunlap
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=507DC0F7.207@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=quartz.jang@samsung.com \
--cc=sangwook.lee@linaro.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.