From: Ben Widawsky <ben@bwidawsk.net>
To: intel-gfx@lists.freedesktop.org
Cc: Ben Widawsky <ben@bwidawsk.net>
Subject: [PATCH 0/9] i915 fixes for sparse warnings.
Date: Mon, 16 Apr 2012 14:07:39 -0700 [thread overview]
Message-ID: <1334610468-9274-1-git-send-email-ben@bwidawsk.net> (raw)
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.
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
next reply other threads:[~2012-04-16 21:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 21:07 Ben Widawsky [this message]
2012-04-16 21:07 ` [PATCH 1/9] drm/i915: [sparse] trivial sparse fixes Ben Widawsky
2012-04-16 21:13 ` Chris Wilson
2012-04-16 21:07 ` [PATCH 2/9] drm/i915: [sparse] don't use variable size arrays Ben Widawsky
2012-04-18 1:39 ` Paulo Zanoni
2012-04-18 2:20 ` Ben Widawsky
2012-04-18 9:05 ` Daniel Vetter
2012-04-16 21:07 ` [PATCH 3/9] drm/i915: [sparse] __iomem fixes for opregion Ben Widawsky
2012-04-16 21:07 ` [PATCH 4/9] drm/i915: [sparse] __iomem fixes for overlay Ben Widawsky
2012-04-16 21:07 ` [PATCH 5/9] drm/i915: [sparse] __iomem fixes for debugfs Ben Widawsky
2012-04-16 21:07 ` [PATCH 6/9] drm/i915: [sparse] __iomem fixes for ringbuffer Ben Widawsky
2012-04-16 21:28 ` Chris Wilson
2012-04-16 21:07 ` [PATCH 7/9] drm/i915: [sparse] forced __iomem ringbuffer fixes Ben Widawsky
2012-04-16 21:07 ` [PATCH 8/9] drm/i915: [sparse] __iomem fixes for gem Ben Widawsky
2012-04-16 21:07 ` [PATCH 9/9] drm/i915: [sparse] __iomem fixes for intel_bios Ben Widawsky
2012-04-21 20:59 ` [PATCH 0/9] i915 fixes for sparse warnings Daniel Vetter
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=1334610468-9274-1-git-send-email-ben@bwidawsk.net \
--to=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.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