All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [PATCH 0/6] drm/i915: introduce platform enum
Date: Wed, 30 Nov 2016 17:43:00 +0200	[thread overview]
Message-ID: <cover.1480520526.git.jani.nikula@intel.com> (raw)

The platform enum patch + some sugar coating on top.

BR,
Jani.

Jani Nikula (6):
  drm/i915: replace platform flags with a platform enum
  drm/i915: keep intel device info structs in gen based order
  drm/i915: rename BROADWATER and CRESTLINE to I965G and I965GM,
    respectively
  drm/i915: add some more "i" in platform names for consistency
  drm/i915: give G45 and GM45 their own platform enums
  drm/i915: use platform enum instead of duplicating PCI ID if possible

 drivers/gpu/drm/i915/i915_debugfs.c      |  5 +-
 drivers/gpu/drm/i915/i915_drv.c          |  2 +-
 drivers/gpu/drm/i915/i915_drv.h          | 92 +++++++++++++++++++-------------
 drivers/gpu/drm/i915/i915_gem.c          |  2 +-
 drivers/gpu/drm/i915/i915_gem_internal.c |  2 +-
 drivers/gpu/drm/i915/i915_gem_stolen.c   |  2 +-
 drivers/gpu/drm/i915/i915_gpu_error.c    |  1 +
 drivers/gpu/drm/i915/i915_pci.c          | 85 ++++++++++++++++-------------
 drivers/gpu/drm/i915/intel_device_info.c | 41 +++++++++++++-
 drivers/gpu/drm/i915/intel_display.c     | 22 ++++----
 drivers/gpu/drm/i915/intel_i2c.c         |  2 +-
 drivers/gpu/drm/i915/intel_overlay.c     |  4 +-
 drivers/gpu/drm/i915/intel_pm.c          |  6 +--
 drivers/gpu/drm/i915/intel_ringbuffer.c  |  4 +-
 14 files changed, 170 insertions(+), 100 deletions(-)

-- 
2.1.4

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

             reply	other threads:[~2016-11-30 15:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 15:43 Jani Nikula [this message]
2016-11-30 15:43 ` [PATCH 1/6] drm/i915: replace platform flags with a platform enum Jani Nikula
2016-12-01  7:54   ` Joonas Lahtinen
2016-12-01 12:49   ` [PATCH v3] " Jani Nikula
2016-12-07  9:51     ` Joonas Lahtinen
2016-12-07 10:09       ` Jani Nikula
2016-12-07 13:23         ` Jani Nikula
2016-11-30 15:43 ` [PATCH 2/6] drm/i915: keep intel device info structs in gen based order Jani Nikula
2016-12-07 10:37   ` Joonas Lahtinen
2016-11-30 15:43 ` [PATCH 3/6] drm/i915: rename BROADWATER and CRESTLINE to I965G and I965GM, respectively Jani Nikula
2016-12-01  8:07   ` Joonas Lahtinen
2016-12-07 10:13   ` [PATCH v2] " Jani Nikula
2016-11-30 15:43 ` [PATCH 4/6] drm/i915: add some more "i" in platform names for consistency Jani Nikula
2016-12-01  8:03   ` Joonas Lahtinen
2016-11-30 15:43 ` [PATCH 5/6] drm/i915: give G45 and GM45 their own platform enums Jani Nikula
2016-12-01  7:58   ` Joonas Lahtinen
2016-11-30 15:43 ` [PATCH 6/6] drm/i915: use platform enum instead of duplicating PCI ID if possible Jani Nikula
2016-12-01  8:00   ` Joonas Lahtinen
2016-12-01  4:15 ` ✓ Fi.CI.BAT: success for drm/i915: introduce platform enum Patchwork
2016-12-01 13:15 ` ✓ Fi.CI.BAT: success for drm/i915: introduce platform enum (rev2) Patchwork
2016-12-07 12:15 ` ✓ Fi.CI.BAT: success for drm/i915: introduce platform enum (rev3) 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=cover.1480520526.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.