From: Jani Nikula <jani.nikula@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Matthew Brost" <matthew.brost@intel.com>,
"Dave Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona.vetter@ffwll.ch>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Maxime Ripard" <mripard@kernel.org>,
"Oded Gabbay" <ogabbay@kernel.org>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, dim-tools@lists.freedesktop.org
Subject: Re: [PULL] topic/step for i915 and xe
Date: Fri, 10 Apr 2026 11:06:12 +0300 [thread overview]
Message-ID: <404ea596f4aacf999d403182d31843a5d2c47bb2@intel.com> (raw)
In-Reply-To: <ade396UuRQoPLGdS@intel.com>
On Thu, 09 Apr 2026, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> On Thu, Apr 09, 2026 at 11:02:20AM +0300, Jani Nikula wrote:
>>
>> Hi Thomas, Matthew and Rodrigo -
>>
>> Here's a topic pull intended for both drm-xe-next and drm-intel-next to
>> unify the steppings header and enum between the i915 and xe drivers. I'm
>> opting for a topic branch because merging this through either driver's
>> -next branch would likely be painful conflicts wise.
>>
>> Please pull this to drm-xe-next (*), and once you're done, I'll follow
>> suit in drm-intel-next.
>
> Pulled to drm-xe-next while I'm covering for Thomas.
And pulled to drm-intel-next as well. Thanks a lot.
BR,
Jani.
>
>>
>> Thanks,
>> Jani.
>>
>>
>> (*) Hint, 'dim apply-pull drm-xe-next' on this message will do the
>> trick.
>>
>>
>> The following changes since commit 4516432284e1b2ad9e70de8067f779c9c1072189:
>>
>> ttm/pool: track allocated_pages per numa node. (2026-04-08 06:52:48 +1000)
>>
>> are available in the Git repository at:
>>
>> https://gitlab.freedesktop.org/drm/i915/kernel.git tags/topic/step-2026-04-09
>>
>> for you to fetch changes up to baf310b9836445ca9056f04ec347293963a1cc6e:
>>
>> drm/i915/display: switch to including common step file directly (2026-04-09 10:10:03 +0300)
>>
>> ----------------------------------------------------------------
>> topic/step to unify xe and i915 on common steppings header and enum
>>
>> ----------------------------------------------------------------
>> Jani Nikula (3):
>> drm/xe/step: switch to the shared step definitions with i915
>> drm/xe/step: switch from enum xe_step to intel_step naming
>> drm/i915/display: switch to including common step file directly
>>
>> drivers/gpu/drm/i915/display/intel_cdclk.c | 2 +-
>> drivers/gpu/drm/i915/display/intel_ddi.c | 2 +-
>> .../gpu/drm/i915/display/intel_display_device.c | 2 +-
>> drivers/gpu/drm/i915/display/intel_display_power.c | 2 +-
>> drivers/gpu/drm/i915/display/intel_display_wa.c | 2 +-
>> drivers/gpu/drm/i915/display/intel_dp_mst.c | 2 +-
>> drivers/gpu/drm/i915/display/intel_dpll_mgr.c | 2 +-
>> drivers/gpu/drm/i915/display/intel_fbc.c | 2 +-
>> drivers/gpu/drm/i915/display/intel_flipq.c | 2 +-
>> drivers/gpu/drm/i915/display/intel_hdcp.c | 2 +-
>> drivers/gpu/drm/i915/display/intel_pmdemand.c | 2 +-
>> drivers/gpu/drm/i915/display/intel_psr.c | 2 +-
>> drivers/gpu/drm/i915/display/skl_universal_plane.c | 2 +-
>> .../gpu/drm/xe/compat-i915-headers/intel_step.h | 13 -----
>> drivers/gpu/drm/xe/tests/xe_pci.c | 4 +-
>> drivers/gpu/drm/xe/xe_step.c | 2 +-
>> drivers/gpu/drm/xe/xe_step.h | 4 +-
>> drivers/gpu/drm/xe/xe_step_types.h | 61 +---------------------
>> 18 files changed, 20 insertions(+), 90 deletions(-)
>> delete mode 100644 drivers/gpu/drm/xe/compat-i915-headers/intel_step.h
>>
>> --
>> Jani Nikula, Intel
--
Jani Nikula, Intel
prev parent reply other threads:[~2026-04-10 8:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 8:02 [PULL] topic/step for i915 and xe Jani Nikula
2026-04-09 14:30 ` Rodrigo Vivi
2026-04-10 8:06 ` Jani Nikula [this message]
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=404ea596f4aacf999d403182d31843a5d2c47bb2@intel.com \
--to=jani.nikula@intel.com \
--cc=airlied@gmail.com \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=mripard@kernel.org \
--cc=ogabbay@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona.vetter@ffwll.ch \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
/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