From: Randy Dunlap <randy.dunlap@oracle.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Haojian Zhuang <haojian.zhuang@marvell.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: [PATCH -next] regulator: fix 88pm8607.c printk format warning
Date: Thu, 26 May 2011 10:16:15 -0700 [thread overview]
Message-ID: <20110526101615.61d5ed27.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110526170756.GA20068@sortiz-mobl>
From: Randy Dunlap <randy.dunlap@oracle.com>
Fix printk format warning (seen on x86_64) and change to unsigned
output format:
drivers/regulator/88pm8607.c:417: warning: format '%d' expects type 'int', but argument 3 has type 'resource_size_t'
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
---
drivers/regulator/88pm8607.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux-next-20110518.orig/drivers/regulator/88pm8607.c
+++ linux-next-20110518/drivers/regulator/88pm8607.c
@@ -413,8 +413,8 @@ static int __devinit pm8607_regulator_pr
break;
}
if ((i < 0) || (i > PM8607_ID_RG_MAX)) {
- dev_err(&pdev->dev, "Failed to find regulator %d\n",
- res->start);
+ dev_err(&pdev->dev, "Failed to find regulator %llu\n",
+ (unsigned long long)res->start);
return -EINVAL;
}
info->i2c = (chip->id == CHIP_PM8607) ? chip->client : chip->companion;
next prev parent reply other threads:[~2011-05-26 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 4:54 linux-next: Tree for May 18 Stephen Rothwell
2011-05-18 17:07 ` [PATCH -next] regulator: fix 88pm8607.c printk format warning Randy Dunlap
2011-05-18 19:43 ` Mark Brown
2011-05-21 11:51 ` Liam Girdwood
2011-05-26 16:05 ` Randy Dunlap
2011-05-26 17:07 ` Samuel Ortiz
2011-05-26 17:16 ` Randy Dunlap [this message]
2011-05-26 18:00 ` Samuel Ortiz
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=20110526101615.61d5ed27.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=haojian.zhuang@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=sameo@linux.intel.com \
--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 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).