From: Jani Nikula <jani.nikula@intel.com>
To: Gustavo Sousa <gustavo.sousa@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 0/4] drm/{i915, xe}: convert i915->display and xe->display into pointers
Date: Fri, 16 May 2025 11:32:30 +0300 [thread overview]
Message-ID: <87y0uxvtup.fsf@intel.com> (raw)
In-Reply-To: <174662247594.2473.11365997948191677836@intel.com>
On Wed, 07 May 2025, Gustavo Sousa <gustavo.sousa@intel.com> wrote:
> Quoting Jani Nikula (2025-05-07 06:38:32-03:00)
>>Another small step towards separating i915 and xe drivers from
>>display. Convert the i915->display and xe->display members into
>>pointers. In the future, we can allocate them dynamically, but one step
>>at a time.
>>
>>BR,
>>Jani.
>>
>>
>>Jani Nikula (4):
>> drm/xe/rpm: use to_xe_device() instead of container_of
>> drm/xe/display: do not reference xe->display inline
>> drm/i915: do not reference i915->display inline
>> drm/{i915,xe}: convert i915 and xe display members into pointers
>
> Series is
>
> Reviewed-by: Gustavo Sousa <gustavo.sousa@intel.com>
Thanks, merged to drm-intel-next.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-05-16 8:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 9:38 [PATCH 0/4] drm/{i915, xe}: convert i915->display and xe->display into pointers Jani Nikula
2025-05-07 9:38 ` [PATCH 1/4] drm/xe/rpm: use to_xe_device() instead of container_of Jani Nikula
2025-05-07 9:38 ` [PATCH 2/4] drm/xe/display: do not reference xe->display inline Jani Nikula
2025-05-07 9:38 ` [PATCH 3/4] drm/i915: do not reference i915->display inline Jani Nikula
2025-05-07 9:38 ` [PATCH 4/4] drm/{i915, xe}: convert i915 and xe display members into pointers Jani Nikula
2025-05-07 15:22 ` [PATCH v2] " Jani Nikula
2025-05-07 10:41 ` ✗ Fi.CI.CHECKPATCH: warning for drm/{i915, xe}: convert i915->display and xe->display " Patchwork
2025-05-07 10:41 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-05-07 11:03 ` ✓ i915.CI.BAT: success " Patchwork
2025-05-07 12:54 ` [PATCH 0/4] " Gustavo Sousa
2025-05-16 8:32 ` Jani Nikula [this message]
2025-05-07 14:44 ` ✗ i915.CI.Full: failure for " Patchwork
2025-05-07 17:04 ` ✓ CI.Patch_applied: success for drm/{i915, xe}: convert i915->display and xe->display into pointers (rev2) Patchwork
2025-05-07 17:05 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-07 17:06 ` ✓ CI.KUnit: success " Patchwork
2025-05-07 17:14 ` ✓ CI.Build: " Patchwork
2025-05-07 17:17 ` ✓ CI.Hooks: " Patchwork
2025-05-07 17:18 ` ✓ CI.checksparse: " Patchwork
2025-05-07 17:41 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-07 19:51 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2025-05-07 19:52 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-05-07 20:18 ` ✓ i915.CI.BAT: success " Patchwork
2025-05-07 20:19 ` Patchwork
2025-05-07 22:28 ` ✗ i915.CI.Full: failure " Patchwork
2025-05-08 13:27 ` ✓ Xe.CI.Full: success " Patchwork
2025-05-26 17:23 ` ✗ CI.Patch_applied: 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=87y0uxvtup.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=gustavo.sousa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--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 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.