From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754453AbcIILzm (ORCPT ); Fri, 9 Sep 2016 07:55:42 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:60772 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753028AbcIILzk (ORCPT ); Fri, 9 Sep 2016 07:55:40 -0400 Date: Fri, 9 Sep 2016 13:55:45 +0200 From: Greg Kroah-Hartman To: Nick Warne Cc: Daniel Vetter , linux-kernel@vger.kernel.org Subject: Re: drivers/gpu/drm/i915/intel_display.c:2954:11: warning: cast to pointer Message-ID: <20160909115545.GB26577@kroah.com> References: <20160907173852.327bb2b3@palantirII.linicks.net> <20160908062937.GC4185@kroah.com> <20160908165953.7fa7828d@palantirII.linicks.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20160908165953.7fa7828d@palantirII.linicks.net> User-Agent: Mutt/1.7.0 (2016-08-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 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? And is this a real bug in 4.4 or just a build warning? thanks, greg k-h