All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com, lucas.demarchi@intel.com
Subject: [PATCH 0/6] drm/i915 and drm/xe display integration cleanups
Date: Fri,  5 Apr 2024 22:37:37 +0300	[thread overview]
Message-ID: <cover.1712345787.git.jani.nikula@intel.com> (raw)

Some cleanups on i915 side, and subsequent cleanups on xe side. I'd like
to merge all of these via drm-intel-next.

BR,
Jani.

Jani Nikula (6):
  drm/i915: use IS_JASPERLAKE()/IS_ELKHARTLAKE() instead of
    IS_PLATFORM()
  drm/i915/dmc: define firmware URL locally
  drm/i915: move i915_fixed.h to display/intel_fixed.h
  drm/xe/display: clean up a lot of cruft from compat i915_drv.h
  drm/xe/display: remove compat i915_gem.h
  drm/xe/display: clean up compat i915_vgpu.h

 .../drm/i915/display/intel_ddi_buf_trans.c    |  4 +--
 drivers/gpu/drm/i915/display/intel_dmc.c      |  4 ++-
 .../{i915_fixed.h => display/intel_fixed.h}   |  0
 drivers/gpu/drm/i915/display/skl_watermark.c  |  2 +-
 .../gpu/drm/xe/compat-i915-headers/i915_drv.h | 34 -------------------
 .../drm/xe/compat-i915-headers/i915_fixed.h   |  6 ----
 .../gpu/drm/xe/compat-i915-headers/i915_gem.h |  9 -----
 .../drm/xe/compat-i915-headers/i915_vgpu.h    | 26 --------------
 .../drm/xe/compat-i915-headers/intel_uc_fw.h  | 11 ------
 9 files changed, 6 insertions(+), 90 deletions(-)
 rename drivers/gpu/drm/i915/{i915_fixed.h => display/intel_fixed.h} (100%)
 delete mode 100644 drivers/gpu/drm/xe/compat-i915-headers/i915_fixed.h
 delete mode 100644 drivers/gpu/drm/xe/compat-i915-headers/i915_gem.h
 delete mode 100644 drivers/gpu/drm/xe/compat-i915-headers/intel_uc_fw.h

-- 
2.39.2


             reply	other threads:[~2024-04-05 19:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 19:37 Jani Nikula [this message]
2024-04-05 19:37 ` [PATCH 1/6] drm/i915: use IS_JASPERLAKE()/IS_ELKHARTLAKE() instead of IS_PLATFORM() Jani Nikula
2024-04-05 19:37 ` [PATCH 2/6] drm/i915/dmc: define firmware URL locally Jani Nikula
2024-04-05 20:27   ` Lucas De Marchi
2024-04-08 16:00     ` Josh Boyer
2024-04-05 19:37 ` [PATCH 3/6] drm/i915: move i915_fixed.h to display/intel_fixed.h Jani Nikula
2024-04-05 19:37 ` [PATCH 4/6] drm/xe/display: clean up a lot of cruft from compat i915_drv.h Jani Nikula
2024-04-05 19:37 ` [PATCH 5/6] drm/xe/display: remove compat i915_gem.h Jani Nikula
2024-04-05 19:37 ` [PATCH 6/6] drm/xe/display: clean up compat i915_vgpu.h Jani Nikula
2024-04-05 20:04 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915 and drm/xe display integration cleanups Patchwork
2024-04-05 20:04 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-04-05 20:10 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-05 20:33 ` [PATCH 0/6] " Lucas De Marchi
2024-04-08  8:07   ` Jani Nikula
2024-04-05 21:41 ` ✓ CI.Patch_applied: success for " Patchwork
2024-04-05 21:41 ` ✗ CI.checkpatch: warning " Patchwork
2024-04-05 21:43 ` ✓ CI.KUnit: success " Patchwork
2024-04-05 21:54 ` ✓ CI.Build: " Patchwork
2024-04-05 21:57 ` ✓ CI.Hooks: " Patchwork
2024-04-05 21:58 ` ✗ CI.checksparse: warning " Patchwork
2024-04-05 22:23 ` ✓ CI.BAT: success " Patchwork
2024-04-06  2:04 ` ✗ Fi.CI.IGT: failure " 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.1712345787.git.jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    /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.