From: Bernhard Walle <bwalle@suse.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH -next] firmware: fix memmap printk format warnings
Date: Sun, 13 Jul 2008 00:17:35 +0200 [thread overview]
Message-ID: <20080713001735.70a33e9e@kopernikus.site> (raw)
In-Reply-To: <20080711125836.59cb0c04.randy.dunlap@oracle.com>
* Randy Dunlap <randy.dunlap@oracle.com> [2008-07-11 12:58]:
>
> From: Randy Dunlap <randy.dunlap@oracle.com>
> cc: Bernhard Walle <bwalle@suse.de>
>
> Fix firmware/memmap printk format warnings:
>
> linux-next-20080711/drivers/firmware/memmap.c:156: warning: format '%llx' expects type 'long long unsigned int', but argument 4 has type 'resource_size_t'
> linux-next-20080711/drivers/firmware/memmap.c:161: warning: format '%llx' expects type 'long long unsigned int', but argument 4 has type 'resource_size_t'
Thanks for the patch. I did not include that change in my cleanup sent
to Andrew to not conflict with that patch.
Bernhard
--
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development
prev parent reply other threads:[~2008-07-12 22:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 19:58 Randy Dunlap
2008-07-12 22:17 ` Bernhard Walle [this message]
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=20080713001735.70a33e9e@kopernikus.site \
--to=bwalle@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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
all inboxes | Powered by JetHome®