Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	rodrigo.vivi@intel.com, ville.syrjala@linux.intel.com
Subject: Re: [PATCH 2/3] drm/xe: remove compat i915_drv.h and -Ddrm_i915_private=xe_device hack
Date: Tue, 30 Dec 2025 23:24:07 +0200	[thread overview]
Message-ID: <00447b0453e8cfbadef56a8c6ca99dfd1fe9d9c4@intel.com> (raw)
In-Reply-To: <20251230164508.GW4164497@mdroper-desk1.amr.corp.intel.com>

On Tue, 30 Dec 2025, Matt Roper <matthew.d.roper@intel.com> wrote:
> On Tue, Dec 30, 2025 at 03:59:33PM +0200, Jani Nikula wrote:
>> On Mon, 29 Dec 2025, Matt Roper <matthew.d.roper@intel.com> wrote:
>> > On Mon, Dec 29, 2025 at 01:54:44PM +0200, Jani Nikula wrote:
>> >> The xe display build no longer needs the compat i915_drv.h or the ugly
>> >> -Ddrm_i915_private=xe_device hack. Remove them, with great pleasure.
>> >> 
>> >> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> >
>> > There's still a comment referring to this aliasing in xe_device_types.h
>> > (above the intel_uncore substruct) that should probably be removed too
>> > now that the alias is gone.  Otherwise,
>> 
>> I already looked at it, but Ville's going to nuke the whole uncore
>> member from xe_device soonish, along with the whole comment, so decided
>> to just let it be. That okay with you?
>
> Yeah, that's fine with me.

Thanks, pushed to drm-intel-next. \o/

BR,
Jani.


-- 
Jani Nikula, Intel

  reply	other threads:[~2025-12-30 21:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-29 11:54 [PATCH 0/3] drm/{i915, xe}/display: remove the -Ddrm_i915_private=xe_device hack Jani Nikula
2025-12-29 11:54 ` [PATCH 1/3] drm/i915: drop i915 param from i915_fence{, _context}_timeout() Jani Nikula
2025-12-29 16:57   ` Matt Roper
2025-12-29 11:54 ` [PATCH 2/3] drm/xe: remove compat i915_drv.h and -Ddrm_i915_private=xe_device hack Jani Nikula
2025-12-29 17:23   ` Matt Roper
2025-12-30 13:59     ` Jani Nikula
2025-12-30 16:45       ` Matt Roper
2025-12-30 21:24         ` Jani Nikula [this message]
2025-12-29 11:54 ` [PATCH 3/3] drm/i915/utils: drop unnecessary ifdefs Jani Nikula
2025-12-29 17:24   ` Matt Roper
2025-12-29 12:01 ` ✗ CI.checkpatch: warning for drm/{i915, xe}/display: remove the -Ddrm_i915_private=xe_device hack Patchwork
2025-12-29 12:02 ` ✓ CI.KUnit: success " Patchwork
2025-12-29 12:41 ` ✓ Xe.CI.BAT: " Patchwork
2025-12-29 14:19 ` ✗ Xe.CI.Full: 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=00447b0453e8cfbadef56a8c6ca99dfd1fe9d9c4@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=ville.syrjala@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox