From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Vetter Subject: Re: [PATCH 0/9] i915 fixes for sparse warnings. Date: Sat, 21 Apr 2012 22:59:25 +0200 Message-ID: <20120421205925.GM5019@phenom.ffwll.local> References: <1334610468-9274-1-git-send-email-ben@bwidawsk.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-we0-f177.google.com (mail-we0-f177.google.com [74.125.82.177]) by gabe.freedesktop.org (Postfix) with ESMTP id 607279E794 for ; Sat, 21 Apr 2012 13:58:26 -0700 (PDT) Received: by werp11 with SMTP id p11so8279706wer.36 for ; Sat, 21 Apr 2012 13:58:25 -0700 (PDT) Content-Disposition: inline In-Reply-To: <1334610468-9274-1-git-send-email-ben@bwidawsk.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Ben Widawsky Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Mon, Apr 16, 2012 at 02:07:39PM -0700, Ben Widawsky wrote: > Patch 1/2 is a mix of fairly trivial stuff. I see no reason to not take > these. > Patch 3-9 Are all __iomem related. These should run through some > regression testing. > > Most of the __iomem stuff fell into place fairly easily, but it's > definitely subject to a lot of copy/paste errors, since trying to > automate the replacement didn't workout well. Throughout the patches, I > tried really hard to not force cast things, but a couple of situations > cropped up which gave me no choice. What I hope to achieve by that is > there should be no functional or performance changes (aside from > copy/paste). > > I've given up on fixing intel_bios.c completely. > > These are based off of dinq as of yesterday. Ok, after some lengthy irc bikeshedding with Ben and Chris I've picked up a few more of these, but changed a few things: - Any hunk that touched the status_page got dropped. I've looked around and I think I have a plan to fix that disaster for real. - Added comments about pointer casts due to sparse. - Dropped the intel_bios.c patch, we agreed that to be too horrible. This needs some serious care to be sparse-compliant. Thanks for digging through this mess. -Daniel > > > Ben Widawsky (9): > drm/i915: [sparse] trivial sparse fixes > drm/i915: [sparse] don't use variable size arrays > drm/i915: [sparse] __iomem fixes for opregion > drm/i915: [sparse] __iomem fixes for overlay > drm/i915: [sparse] __iomem fixes for debugfs > drm/i915: [sparse] __iomem fixes for ringbuffer > drm/i915: [sparse] forced __iomem ringbuffer fixes > drm/i915: [sparse] __iomem fixes for gem > drm/i915: [sparse] __iomem fixes for intel_bios > > drivers/gpu/drm/i915/i915_debugfs.c | 28 ++++--- > drivers/gpu/drm/i915/i915_drv.h | 12 +-- > drivers/gpu/drm/i915/i915_gem.c | 11 +-- > drivers/gpu/drm/i915/i915_ioc32.c | 5 +- > drivers/gpu/drm/i915/i915_trace_points.c | 2 + > drivers/gpu/drm/i915/intel_acpi.c | 1 + > drivers/gpu/drm/i915/intel_bios.c | 20 +++-- > drivers/gpu/drm/i915/intel_display.c | 2 +- > drivers/gpu/drm/i915/intel_fb.c | 2 +- > drivers/gpu/drm/i915/intel_opregion.c | 67 ++++++++------- > drivers/gpu/drm/i915/intel_overlay.c | 130 +++++++++++++++++------------- > drivers/gpu/drm/i915/intel_ringbuffer.c | 28 ++++--- > drivers/gpu/drm/i915/intel_sdvo.c | 26 ++++-- > 13 files changed, 197 insertions(+), 137 deletions(-) > > -- > 1.7.10 > > _______________________________________________ > Intel-gfx mailing list > Intel-gfx@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/intel-gfx -- Daniel Vetter Mail: daniel@ffwll.ch Mobile: +41 (0)79 365 57 48