From: Jeff Garzik <jeff@garzik.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: amitkale@netxen.com, Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org
Subject: Re: [NET] netxen: fix warnings
Date: Fri, 09 Mar 2007 11:47:50 -0500 [thread overview]
Message-ID: <45F18FB6.2090701@garzik.org> (raw)
In-Reply-To: <20070306203537.GA5822@linux-mips.org>
Ralf Baechle wrote:
> CC [M] drivers/net/netxen/netxen_nic_hw.o
> drivers/net/netxen/netxen_nic_hw.c: In function 'netxen_nic_hw_resources':
> drivers/net/netxen/netxen_nic_hw.c:231: warning: format '%llx' expects type 'long long unsigned int', but argument 2 has type 'dma_addr_t'
> drivers/net/netxen/netxen_nic_hw.c:250: warning: format '%llx' expects type 'long long unsigned int', but argument 2 has type 'dma_addr_t'
>
> u64 is unsigned long so the cast to u64 will result in a warning on the
> printf arguments for 64-bit builds. So cast to unsigned long long instead.
>
> Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
applied
prev parent reply other threads:[~2007-03-09 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 20:35 [NET] netxen: fix warnings Ralf Baechle
2007-03-09 16:47 ` Jeff Garzik [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=45F18FB6.2090701@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=amitkale@netxen.com \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.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;
as well as URLs for NNTP newsgroup(s).