From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Tiago Vignatti <tiago.vignatti@nokia.com>,
Dave Airlie <airlied@redhat.com>
Subject: Re: linux-next: pci tree build warning
Date: Thu, 13 Aug 2009 13:32:40 +1000 [thread overview]
Message-ID: <1250134360.3587.77.camel@pasglop> (raw)
In-Reply-To: <20090813124732.f29fd5c3.sfr@canb.auug.org.au>
On Thu, 2009-08-13 at 12:47 +1000, Stephen Rothwell wrote:
> Hi Jesse,
>
> Today's linux-next build (x86_64 allmodconfig) produced these warnings:
>
> drivers/gpu/vga/vgaarb.c: In function 'vga_arb_write':
> drivers/gpu/vga/vgaarb.c:834: warning: cast from pointer to integer of different size
> drivers/gpu/vga/vgaarb.c:870: warning: cast from pointer to integer of different size
> drivers/gpu/vga/vgaarb.c:920: warning: cast from pointer to integer of different size
> drivers/gpu/vga/vgaarb.c:963: warning: cast from pointer to integer of different size
> drivers/gpu/vga/vgaarb.c:1017: warning: cast from pointer to integer of different size
>
> Introduced by commit a49c9c1b728fa8f50816d96a0f135e15a359e448 ("PCI/GPU:
> implement VGA arbitration on Linux").
Right, somebody weirdly decided to cast pointers to int just to printk
them with %X :-) I hope it wasn't me ...
Just remove the casts and use %p instead.
Cheers,
Ben.
next prev parent reply other threads:[~2009-08-13 3:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 2:47 linux-next: pci tree build warning Stephen Rothwell
2009-08-13 3:32 ` Benjamin Herrenschmidt [this message]
2009-08-13 8:38 ` Vignatti Tiago (Nokia-D/Helsinki)
-- strict thread matches above, loose matches on Subject: below --
2009-10-08 4:27 Stephen Rothwell
2009-05-06 4:30 Stephen Rothwell
2009-05-06 7:21 ` Yinghai Lu
2009-02-18 6:31 Stephen Rothwell
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=1250134360.3587.77.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=airlied@redhat.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tiago.vignatti@nokia.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;
as well as URLs for NNTP newsgroup(s).