From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 00/11] drm/{i915, xe}/stolen: refactor and unify interfaces
Date: Fri, 26 Sep 2025 21:41:16 +0300 [thread overview]
Message-ID: <aNbeTOg51r9puj4i@intel.com> (raw)
In-Reply-To: <cover.1758732183.git.jani.nikula@intel.com>
On Wed, Sep 24, 2025 at 07:43:29PM +0300, Jani Nikula wrote:
>
> Jani Nikula (11):
> drm/{i915,xe}/stolen: rename i915_stolen_fb to intel_stolen_node
> drm/xe/stolen: rename fb to node in stolen compat header
> drm/xe/stolen: convert compat stolen macros to inline functions
> drm/xe/stolen: switch from BUG_ON() to WARN_ON() in compat
> drm/i915/stolen: convert intel_stolen_node into a real struct of its
> own
> drm/xe/stolen: convert compat static inlines to proper functions
> drm/{i915,xe}/stolen: make struct intel_stolen_node opaque
> drm/{i915,xe}/stolen: add device pointer to struct intel_stolen_node
> drm/{i915,xe}/stolen: use the stored i915/xe device pointer
> drm/{i915,xe}/stolen: convert stolen interface to struct drm_device
> drm/xe/stolen: use the same types as i915 interface
Looks fine by me. Series is
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Side note: I have branch somewhere that replaces the raw
drm_mm_node FBC stuff with a real i915_gem_object. I used
that as a way to easily expose the CFB and LLB as files in
debugfs so that I could observe/modify the actual CFB contents.
I should look into making that official to help future FBC
debugging. With the abstraction layer I shouldn't even need
to touch the FBC code itself anymore...
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2025-09-26 18:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 16:43 [PATCH 00/11] drm/{i915,xe}/stolen: refactor and unify interfaces Jani Nikula
2025-09-24 16:43 ` [PATCH 01/11] drm/{i915, xe}/stolen: rename i915_stolen_fb to intel_stolen_node Jani Nikula
2025-09-24 16:43 ` [PATCH 02/11] drm/xe/stolen: rename fb to node in stolen compat header Jani Nikula
2025-09-24 16:43 ` [PATCH 03/11] drm/xe/stolen: convert compat stolen macros to inline functions Jani Nikula
2025-09-24 16:43 ` [PATCH 04/11] drm/xe/stolen: switch from BUG_ON() to WARN_ON() in compat Jani Nikula
2025-09-24 16:43 ` [PATCH 05/11] drm/i915/stolen: convert intel_stolen_node into a real struct of its own Jani Nikula
2025-09-24 16:43 ` [PATCH 06/11] drm/xe/stolen: convert compat static inlines to proper functions Jani Nikula
2025-09-24 16:43 ` [PATCH 07/11] drm/{i915, xe}/stolen: make struct intel_stolen_node opaque Jani Nikula
2025-09-24 16:43 ` [PATCH 08/11] drm/{i915, xe}/stolen: add device pointer to struct intel_stolen_node Jani Nikula
2025-09-24 16:43 ` [PATCH 09/11] drm/{i915, xe}/stolen: use the stored i915/xe device pointer Jani Nikula
2025-09-24 16:43 ` [PATCH 10/11] drm/{i915, xe}/stolen: convert stolen interface to struct drm_device Jani Nikula
2025-09-24 16:43 ` [PATCH 11/11] drm/xe/stolen: use the same types as i915 interface Jani Nikula
2025-09-24 17:03 ` ✗ CI.checkpatch: warning for drm/{i915,xe}/stolen: refactor and unify interfaces Patchwork
2025-09-24 17:04 ` ✓ CI.KUnit: success " Patchwork
2025-09-24 17:19 ` ✗ CI.checksparse: warning " Patchwork
2025-09-24 17:38 ` ✓ Xe.CI.BAT: success " Patchwork
2025-09-24 17:53 ` ✓ i915.CI.BAT: " Patchwork
2025-09-24 22:08 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-25 1:14 ` ✗ i915.CI.Full: " Patchwork
2025-09-26 18:41 ` Ville Syrjälä [this message]
2025-09-29 9:53 ` [PATCH 00/11] drm/{i915, xe}/stolen: " Jani Nikula
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=aNbeTOg51r9puj4i@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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.