From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>,
intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH v2 0/6] Fix compatibility issue for intel_dmc
Date: Thu, 12 Oct 2023 12:08:10 +0300 [thread overview]
Message-ID: <87r0m02op1.fsf@intel.com> (raw)
In-Reply-To: <20231012050645.2058219-1-chaitanya.kumar.borah@intel.com>
On Thu, 12 Oct 2023, Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com> wrote:
> This series reverts hacky #ifdefs from intel_dmc
>
> v2: Rebase
>
> Acked-by: Jani Nikula <jani.nikula@intel.com>
Mmh, come to think of it, the last three patches probably also need to
be fixup! drm/xe/display: Implement display support.
BR,
Jani.
>
> Chaitanya Kumar Borah (6):
> Revert "FIXME: drm/i915/dmc: xe way of getting at stepping"
> drm/i915: Add wrapper for getting display step
> fixup! drm/xe/display: Implement display support
> drm/xe: Add intel_step.h compatibility header
> drm/xe: Add i915_gpu_error.h compatibility header
> drm/xe: Add intel_uc_fw.h compatibility header
>
> drivers/gpu/drm/i915/display/intel_dmc.c | 19 ++----------------
> drivers/gpu/drm/i915/intel_step.c | 5 +++++
> drivers/gpu/drm/i915/intel_step.h | 1 +
> .../gpu/drm/xe/compat-i915-headers/i915_drv.h | 4 +++-
> .../xe/compat-i915-headers/i915_gpu_error.h | 18 +++++++++++++++++
> .../drm/xe/compat-i915-headers/intel_step.h | 20 +++++++++++++++++++
> .../drm/xe/compat-i915-headers/intel_uc_fw.h | 12 +++++++++++
> 7 files changed, 61 insertions(+), 18 deletions(-)
> create mode 100644 drivers/gpu/drm/xe/compat-i915-headers/i915_gpu_error.h
> create mode 100644 drivers/gpu/drm/xe/compat-i915-headers/intel_step.h
> create mode 100644 drivers/gpu/drm/xe/compat-i915-headers/intel_uc_fw.h
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-10-12 9:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 5:06 [Intel-xe] [PATCH v2 0/6] Fix compatibility issue for intel_dmc Chaitanya Kumar Borah
2023-10-12 5:06 ` [Intel-xe] [PATCH 1/6] Revert "FIXME: drm/i915/dmc: xe way of getting at stepping" Chaitanya Kumar Borah
2023-10-12 5:06 ` [Intel-xe] [PATCH 2/6] drm/i915: Add wrapper for getting display step Chaitanya Kumar Borah
2023-10-12 5:06 ` [Intel-xe] [PATCH 3/6] fixup! drm/xe/display: Implement display support Chaitanya Kumar Borah
2023-10-12 5:06 ` [Intel-xe] [PATCH 4/6] drm/xe: Add intel_step.h compatibility header Chaitanya Kumar Borah
2023-10-12 5:06 ` [Intel-xe] [PATCH 5/6] drm/xe: Add i915_gpu_error.h " Chaitanya Kumar Borah
2023-10-12 5:06 ` [Intel-xe] [PATCH 6/6] drm/xe: Add intel_uc_fw.h " Chaitanya Kumar Borah
2023-10-12 5:14 ` [Intel-xe] ✓ CI.Patch_applied: success for Fix compatibility issue for intel_dmc (rev2) Patchwork
2023-10-12 5:14 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-10-12 5:15 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-10-12 5:23 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-10-12 5:23 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-10-12 5:24 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-10-12 5:52 ` [Intel-xe] ✓ CI.BAT: success " Patchwork
2023-10-12 9:08 ` Jani Nikula [this message]
2023-10-12 10:55 ` [Intel-xe] [PATCH v2 0/6] Fix compatibility issue for intel_dmc Borah, Chaitanya Kumar
2023-10-12 11:56 ` Jani Nikula
2023-10-12 13:02 ` Borah, Chaitanya Kumar
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=87r0m02op1.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=intel-xe@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