From: Randy Dunlap <randy.dunlap@oracle.com>
To: Joe Perches <joe@perches.com>
Cc: linux-next@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH -next] PNP: fix printk format warnings
Date: Wed, 30 Apr 2008 14:25:39 -0700 [thread overview]
Message-ID: <4818E3D3.7000907@oracle.com> (raw)
In-Reply-To: <1209589640.5041.67.camel@localhost>
Joe Perches wrote:
> On Wed, 2008-04-30 at 13:56 -0700, Randy Dunlap wrote:
>> From: Randy Dunlap <randy.dunlap@oracle.com>
>>
>> next-20080430/drivers/pnp/pnpbios/rsparser.c:594: warning: format '%d' expects type 'int', but argument 4 has type 'resource_size_t'
>> next-20080430/drivers/pnp/pnpbios/rsparser.c:605: warning: format '%d' expects type 'int', but argument 4 has type 'resource_size_t'
>
> resource_size_t can be u64
I know.
> I think you need %llu/(unsigned long long)
So the interrupt number or DMA channel may be astronomically huge? OK.
Whatever.
> --- next-20080430.orig/drivers/pnp/pnpbios/rsparser.c
> +++ next-20080430/drivers/pnp/pnpbios/rsparser.c
> @@ -591,7 +591,7 @@ static void pnpbios_encode_irq(struct pn
> p[1] = map & 0xff;
> p[2] = (map >> 8) & 0xff;
>
> - dev_dbg(&dev->dev, " encode irq %d\n", res->start);
> + dev_dbg(&dev->dev, " encode irq %llu\n", (unsigned long long)res->start);
> }
>
> static void pnpbios_encode_dma(struct pnp_dev *dev, unsigned char *p,
> @@ -602,7 +602,7 @@ static void pnpbios_encode_dma(struct pn
> map = 1 << res->start;
> p[1] = map & 0xff;
>
> - dev_dbg(&dev->dev, " encode dma %d\n", res->start);
> + dev_dbg(&dev->dev, " encode dma %llu\n", (unsigned long long)res->start);
> }
>
> static void pnpbios_encode_port(struct pnp_dev *dev, unsigned char *p,
>
>
--
~Randy
next prev parent reply other threads:[~2008-04-30 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 20:56 [PATCH -next] PNP: fix printk format warnings Randy Dunlap
2008-04-30 21:07 ` Joe Perches
2008-04-30 21:25 ` Randy Dunlap [this message]
2008-05-04 19:18 ` Rene Herman
2008-05-04 21:05 ` Randy Dunlap
2008-05-04 21:40 ` Rene Herman
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=4818E3D3.7000907@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox