From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Suneel <suneelg@xilinx.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
linux-next@vger.kernel.org, John Linn <john.linn@xilinx.com>
Subject: Re: linux-next: Linus/powerpc tree build warning
Date: Tue, 16 Jun 2009 16:59:46 +1000 [thread overview]
Message-ID: <1245135586.12400.104.camel@pasglop> (raw)
In-Reply-To: <20090616162429.07e74e75.sfr@canb.auug.org.au>
On Tue, 2009-06-16 at 16:24 +1000, Stephen Rothwell wrote:
> Hi Ben,
>
> Today's linux-next build (powerpc ppc44x_defconfig) produced this warning:
>
> drivers/video/xilinxfb.c: In function 'xilinxfb_assign':
> drivers/video/xilinxfb.c:328: warning: cast to pointer from integer of different size
>
> Introduced by commit dac4ccfb64bcdd5b4c248ccc22903d67486573cd ("fbdev:
> Add PLB support and cleanup DCR in xilinxfb driver").
Known problem, a fix is currently being polished by Grant and John.
Cheers,
Ben.
prev parent reply other threads:[~2009-06-16 7:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 6:24 linux-next: Linus/powerpc tree build warning Stephen Rothwell
2009-06-16 6:59 ` Benjamin Herrenschmidt [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=1245135586.12400.104.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=john.linn@xilinx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
--cc=suneelg@xilinx.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).