From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [PATCH 0/9] drm/i915: nuke drm_i915_private_t
Date: Mon, 31 Mar 2014 14:27:13 +0300 [thread overview]
Message-ID: <cover.1396264683.git.jani.nikula@intel.com> (raw)
We've tried to avoid drm_i915_private_t for some time, but new uses keep
creeping in. Should we get rid of it once and for all?
Patches 1-7 are per file, patch 8 has the rest, patch 9 drops the
typedef. The first 8 can be applied in any order. Or squashed together
to reduce the patch count. Or if there are nasty conflicts on the way,
some can be postponed or dropped altogether for now.
BR,
Jani.
Jani Nikula (9):
drm/i915/debugfs: prefer struct drm_i915_private to
drm_i915_private_t
drm/i915/dma: prefer struct drm_i915_private to drm_i915_private_t
drm/i915/gem: prefer struct drm_i915_private to drm_i915_private_t
drm/i915/irq: prefer struct drm_i915_private to drm_i915_private_t
drm/i915/display: prefer struct drm_i915_private to
drm_i915_private_t
drm/i915/ringbuffer: prefer struct drm_i915_private to
drm_i915_private_t
drm/i915/overlay: prefer struct drm_i915_private to
drm_i915_private_t
drm/i915: prefer struct drm_i915_private to drm_i915_private_t
drm/i915: drop the typedef for drm_i915_private_t
drivers/gpu/drm/i915/i915_cmd_parser.c | 2 +-
drivers/gpu/drm/i915/i915_debugfs.c | 46 ++++++------
drivers/gpu/drm/i915/i915_dma.c | 48 ++++++------
drivers/gpu/drm/i915/i915_drv.c | 2 +-
drivers/gpu/drm/i915/i915_drv.h | 10 +--
drivers/gpu/drm/i915/i915_gem.c | 46 ++++++------
drivers/gpu/drm/i915/i915_gem_debug.c | 2 +-
drivers/gpu/drm/i915/i915_gem_evict.c | 4 +-
drivers/gpu/drm/i915/i915_gem_execbuffer.c | 4 +-
drivers/gpu/drm/i915/i915_gem_gtt.c | 4 +-
drivers/gpu/drm/i915/i915_gem_tiling.c | 6 +-
drivers/gpu/drm/i915/i915_gpu_error.c | 2 +-
drivers/gpu/drm/i915/i915_irq.c | 110 ++++++++++++++--------------
drivers/gpu/drm/i915/intel_display.c | 22 +++---
drivers/gpu/drm/i915/intel_overlay.c | 24 +++---
drivers/gpu/drm/i915/intel_pm.c | 4 +-
drivers/gpu/drm/i915/intel_ringbuffer.c | 38 +++++-----
17 files changed, 187 insertions(+), 187 deletions(-)
--
1.7.9.5
next reply other threads:[~2014-03-31 11:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 11:27 Jani Nikula [this message]
2014-03-31 11:27 ` [PATCH 1/9] drm/i915/debugfs: prefer struct drm_i915_private to drm_i915_private_t Jani Nikula
2014-03-31 11:27 ` [PATCH 2/9] drm/i915/dma: " Jani Nikula
2014-03-31 11:27 ` [PATCH 3/9] drm/i915/gem: " Jani Nikula
2014-03-31 11:27 ` [PATCH 4/9] drm/i915/irq: " Jani Nikula
2014-03-31 11:27 ` [PATCH 5/9] drm/i915/display: " Jani Nikula
2014-03-31 11:27 ` [PATCH 6/9] drm/i915/ringbuffer: " Jani Nikula
2014-03-31 11:27 ` [PATCH 7/9] drm/i915/overlay: " Jani Nikula
2014-03-31 11:27 ` [PATCH 8/9] drm/i915: " Jani Nikula
2014-03-31 11:27 ` [PATCH 9/9] drm/i915: drop the typedef for drm_i915_private_t Jani Nikula
2014-03-31 11:35 ` Chris Wilson
2014-03-31 12:28 ` Jani Nikula
2014-03-31 13:48 ` [PATCH 0/9] drm/i915: nuke drm_i915_private_t 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=cover.1396264683.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--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