From: Paul Bolle <pebolle@tiscali.nl>
To: Mike Looijmans <mike.looijmans@topic.nl>
Cc: linux-clk@vger.kernel.org, sboyd@codeaurora.org,
mturquette@linaro.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3] Add TI CDCE925 I2C controlled clock synthesizer driver
Date: Tue, 02 Jun 2015 09:50:44 +0200 [thread overview]
Message-ID: <1433231444.2361.75.camel@x220> (raw)
In-Reply-To: <1433153623-29205-1-git-send-email-mike.looijmans@topic.nl>
On Mon, 2015-06-01 at 12:13 +0200, Mike Looijmans wrote:
> --- /dev/null
> +++ b/drivers/clk/clk-cdce925.c
> +static int cdce925_regmap_i2c_write(
> + void *context, const void *data, size_t count)
> + dev_dbg(&i2c->dev, "%s(%u) %#x %#x\n", __func__, count,
> + reg_data[0], reg_data[1]);
For some silly reason (ie, I mistakenly thought I spotted an issue) I
did a quick build of this file. That triggered some noise on x86_64.
Excerpt:
drivers/clk/clk-cdce925.c: In function ‘cdce925_regmap_i2c_write’:
include/linux/dynamic_debug.h:64:16: warning: format ‘%u’ expects argument of type ‘unsigned int’, but argument 5 has type ‘size_t’ [-Wformat=]
static struct _ddebug __aligned(8) \
^
[...]
drivers/clk/clk-cdce925.c:505:2: note: in expansion of macro ‘dev_dbg’
dev_dbg(&i2c->dev, "%s(%u) %#x %#x\n", __func__, count,
^
A quick look at Documentation/printk-formats.txt suggested this (very
lightly tested) fix:
@@ -502,7 +502,7 @@ static int cdce925_regmap_i2c_write(
reg_data[0] = CDCE925_I2C_COMMAND_BYTE_TRANSFER | ((u8 *)data)[0];
reg_data[1] = ((u8 *)data)[1];
- dev_dbg(&i2c->dev, "%s(%u) %#x %#x\n", __func__, count,
+ dev_dbg(&i2c->dev, "%s(%zu) %#x %#x\n", __func__, count,
reg_data[0], reg_data[1]);
ret = i2c_master_send(i2c, reg_data, count);
> +static int cdce925_regmap_i2c_read(void *context,
> + const void *reg, size_t reg_size, void *val, size_t val_size)
> + dev_dbg(&i2c->dev, "%s(%u, %u) %#x %#x\n", __func__,
> + reg_size, val_size, reg_data[0], *((u8 *)val));
Likewise:
@@ -547,7 +547,7 @@ static int cdce925_regmap_i2c_read(void *context,
ret = i2c_transfer(i2c->adapter, xfer, 2);
if (likely(ret == 2)) {
- dev_dbg(&i2c->dev, "%s(%u, %u) %#x %#x\n", __func__,
+ dev_dbg(&i2c->dev, "%s(%zu, %zu) %#x %#x\n", __func__,
reg_size, val_size, reg_data[0], *((u8 *)val));
return 0;
} else if (ret < 0)
Thanks,
Paul Bolle
next prev parent reply other threads:[~2015-06-02 7:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 10:13 [PATCH v3] Add TI CDCE925 I2C controlled clock synthesizer driver Mike Looijmans
2015-06-01 10:13 ` Mike Looijmans
2015-06-02 7:50 ` Paul Bolle [this message]
2015-06-02 8:39 ` Mike Looijmans
2015-06-02 8:39 ` Mike Looijmans
2015-06-02 8:39 ` Mike Looijmans
2015-06-02 8:43 ` Mike Looijmans
2015-06-02 8:43 ` Mike Looijmans
2015-06-02 8:43 ` Mike Looijmans
2015-06-02 9:07 ` Paul Bolle
2015-06-03 5:25 ` [PATCH v4] " Mike Looijmans
2015-06-03 5:25 ` Mike Looijmans
2015-06-03 22:25 ` Michael Turquette
2015-06-03 22:25 ` Michael Turquette
2015-06-03 22:25 ` Michael Turquette
2015-06-03 22:30 ` Stephen Boyd
2015-06-03 22:30 ` Stephen Boyd
2015-06-03 22:44 ` Michael Turquette
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=1433231444.2361.75.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.looijmans@topic.nl \
--cc=mturquette@linaro.org \
--cc=sboyd@codeaurora.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 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.