From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com, ville.syrjala@linux.intel.com
Subject: [PATCH 00/11] drm/{i915,xe}/stolen: refactor and unify interfaces
Date: Wed, 24 Sep 2025 19:43:29 +0300 [thread overview]
Message-ID: <cover.1758732183.git.jani.nikula@intel.com> (raw)
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
drivers/gpu/drm/i915/display/intel_fbc.c | 76 ++++++-----
drivers/gpu/drm/i915/gem/i915_gem_stolen.c | 104 +++++++++++----
drivers/gpu/drm/i915/gem/i915_gem_stolen.h | 34 +++--
drivers/gpu/drm/xe/Makefile | 1 +
.../compat-i915-headers/gem/i915_gem_stolen.h | 105 +++++----------
drivers/gpu/drm/xe/display/xe_stolen.c | 123 ++++++++++++++++++
6 files changed, 290 insertions(+), 153 deletions(-)
create mode 100644 drivers/gpu/drm/xe/display/xe_stolen.c
--
2.47.3
next reply other threads:[~2025-09-24 16:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 16:43 Jani Nikula [this message]
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 22:08 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-26 18:41 ` [PATCH 00/11] drm/{i915, xe}/stolen: " Ville Syrjälä
2025-09-29 9:53 ` 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=cover.1758732183.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--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;
as well as URLs for NNTP newsgroup(s).