From: Nick Warne <nick@linicks.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Daniel Vetter <daniel.vetter@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: drivers/gpu/drm/i915/intel_display.c:2954:11: warning: cast to pointer
Date: Fri, 9 Sep 2016 13:55:03 +0100 [thread overview]
Message-ID: <20160909135503.02041103@palantirII.linicks.net> (raw)
In-Reply-To: <20160909115545.GB26577@kroah.com>
On Fri, 9 Sep 2016 13:55:45 +0200
Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> On Thu, Sep 08, 2016 at 04:59:53PM +0100, Nick Warne wrote:
> > On Thu, 8 Sep 2016 08:29:37 +0200
> > Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> >
> > > On Wed, Sep 07, 2016 at 05:38:52PM +0100, Nick Warne wrote:
> > > > Hi Daniel,
> > > >
> > > > kernel build 4.4.20 - I am still seeing this warning:
> > > >
> > > > drivers/gpu/drm/i915/intel_display.c: In function
> > > > ‘intel_plane_obj_offset’:
> > > > drivers/gpu/drm/i915/intel_display.c:2969:11: warning: cast to
> > > > pointer from integer of different size [-Wint-to-pointer-cast]
> > > > offset = (unsigned char *)vma->node.start;
> > > >
> > > > but according to here:
> > > >
> > > > https://patchwork.kernel.org/patch/7897461/
> > > >
> > > > this has been fixed up. Any reason why it hasn't in the latest
> > > > 4.4.x longterm tree?
> > >
> > > What is the commit id that fixed this in Linus's tree?
> >
> > Took me a while to find it if this is it - a bit of a re-write in
> > the whole file I think:
> >
> > https://github.com/torvalds/linux/commit/44eb0cb9620c6a53ec8e7073262e2af8079b727f
>
> Ick, messy.
>
> Why not just use 4.7? Why are you stuck at 4.4?
I only recently moved over to 4.4 from 3.18.x as it's longterm
support. I may try 4.7 over the weekend - or maybe even just use the
patchwork diff on my own local builds.
> And is this a real bug in 4.4 or just a build warning?
No, it's not a bug (that I have found or seen, anyway), just GCC
squinnying.
Thanks for your help, and sorry for the noise.
Nick
--
Gosh that takes me back... or is it forward? That's the trouble with
time travel, you never can tell."
-- Doctor Who "Androids of Tara"
next prev parent reply other threads:[~2016-09-09 12:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 16:38 drivers/gpu/drm/i915/intel_display.c:2954:11: warning: cast to pointer Nick Warne
2016-09-08 6:29 ` Greg Kroah-Hartman
2016-09-08 15:59 ` Nick Warne
2016-09-09 11:55 ` Greg Kroah-Hartman
2016-09-09 12:55 ` Nick Warne [this message]
2016-09-10 10:48 ` Nick Warne
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=20160909135503.02041103@palantirII.linicks.net \
--to=nick@linicks.net \
--cc=daniel.vetter@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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