public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: David Weinehall <david.weinehall@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [REBASED PATCH RESEND 0/5 v2] Various cleanup
Date: Mon, 22 Aug 2016 13:32:40 +0300	[thread overview]
Message-ID: <20160822103245.24069-1-david.weinehall@linux.intel.com> (raw)

This patch series aims to do some cleanup of our driver.
Patch 1, 2, and 4 should be fairly non-controversial.
Patch 3 and 5 does major cleanups of i915_sysfs and i915_debugfs,
respectively. Due to the nature of these patches they are rather
big, but that's mainly because they change the parameter passed
to macros that are used a lot.

While the secondary benefits of this patch series (the primary
of course being slightly cleaner code) might be a bit opaque,
a move to always passing dev_priv to our feature macros
(and thus allowing us to make those macros non-polymorphic)
will save more than 30kB.

That's still a bit down the road though, but I've got a full
patch series to accomplish this in a fairly straightforward
manner.

Resend: mailing list issues

David Weinehall (5):
  drm/i915: cosmetic fixes to i915_drv.h
  drm/i915: consistent struct device naming
  drm/i915: i915_sysfs.c cleanup
  drm/i915: pdev cleanup
  drm/i915: debugfs spring cleaning

 drivers/gpu/drm/i915/i915_debugfs.c     | 801 ++++++++++++++------------------
 drivers/gpu/drm/i915/i915_drv.c         | 157 ++++---
 drivers/gpu/drm/i915/i915_drv.h         |  16 +-
 drivers/gpu/drm/i915/i915_gem_gtt.c     |  16 +-
 drivers/gpu/drm/i915/i915_gem_stolen.c  |  19 +-
 drivers/gpu/drm/i915/i915_gpu_error.c   |   9 +-
 drivers/gpu/drm/i915/i915_suspend.c     |   6 +-
 drivers/gpu/drm/i915/i915_sysfs.c       | 163 +++----
 drivers/gpu/drm/i915/intel_audio.c      |  46 +-
 drivers/gpu/drm/i915/intel_display.c    |  25 +-
 drivers/gpu/drm/i915/intel_fbdev.c      |   3 +-
 drivers/gpu/drm/i915/intel_guc_loader.c |   3 +-
 drivers/gpu/drm/i915/intel_i2c.c        |   3 +-
 drivers/gpu/drm/i915/intel_runtime_pm.c |  57 +--
 drivers/gpu/drm/i915/intel_sdvo.c       |   4 +-
 15 files changed, 629 insertions(+), 699 deletions(-)

-- 
2.9.3

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2016-08-22 10:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-22 10:32 David Weinehall [this message]
2016-08-22 10:32 ` [REBASED PATCH RESEND 1/5 v2] drm/i915: cosmetic fixes to i915_drv.h David Weinehall
2016-08-22 10:32 ` [REBASED PATCH RESEND 2/5 v2] drm/i915: consistent struct device naming David Weinehall
2016-08-22 10:32 ` [REBASED PATCH RESEND 3/5 v2] drm/i915: i915_sysfs.c cleanup David Weinehall
2016-08-22 10:32 ` [REBASED PATCH RESEND 4/5 v2] drm/i915: pdev cleanup David Weinehall
2016-08-22 10:32 ` [REBASED PATCH RESEND 5/5 v2] drm/i915: debugfs spring cleaning David Weinehall
2016-08-22 10:59   ` [REBASED PATCH RESEND 5/5 v3] " David Weinehall
2016-08-22 11:04     ` Chris Wilson
2016-08-22 10:38 ` [REBASED PATCH RESEND 0/5 v2] Various cleanup Chris Wilson
2016-08-22 10:53 ` ✗ Ro.CI.BAT: failure for " Patchwork

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=20160822103245.24069-1-david.weinehall@linux.intel.com \
    --to=david.weinehall@linux.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