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 v2 00/10] drm/{i915,xe}/fbdev: refactor
Date: Thu, 18 Sep 2025 11:40:50 +0300 [thread overview]
Message-ID: <cover.1758184771.git.jani.nikula@intel.com> (raw)
v2 of [1], unifying the stride alignment and error paths first, rebasing
the rest on top.
[1] https://lore.kernel.org/r/cover.1756931441.git.jani.nikula@intel.com
Jani Nikula (10):
drm/xe/fbdev: use the same 64-byte stride alignment as i915
drm/i915/fbdev: make intel_framebuffer_create() error return handling
explicit
drm/{i915,xe}/fbdev: pass struct drm_device to intel_fbdev_fb_alloc()
drm/{i915,xe}/fbdev: deduplicate struct drm_mode_fb_cmd2 init
drm/i915/fbdev: abstract bo creation
drm/xe/fbdev: abstract bo creation
drm/{i915,xe}/fbdev: add intel_fbdev_fb_bo_destroy()
drm/{i915,xe}/fbdev: deduplicate fbdev creation
drm/{i915,xe}/fbdev: pass struct drm_device to
intel_fbdev_fb_fill_info()
drm/i915/fbdev: drop dependency on display in i915 specific code
drivers/gpu/drm/i915/display/intel_fbdev.c | 59 ++++++++++++++++++-
drivers/gpu/drm/i915/display/intel_fbdev_fb.c | 51 ++++------------
drivers/gpu/drm/i915/display/intel_fbdev_fb.h | 11 ++--
drivers/gpu/drm/xe/display/intel_fbdev_fb.c | 55 ++++-------------
4 files changed, 86 insertions(+), 90 deletions(-)
--
2.47.3
next reply other threads:[~2025-09-18 8:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 8:40 Jani Nikula [this message]
2025-09-18 8:40 ` [PATCH v2 01/10] drm/xe/fbdev: use the same 64-byte stride alignment as i915 Jani Nikula
2025-09-18 17:38 ` Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 02/10] drm/i915/fbdev: make intel_framebuffer_create() error return handling explicit Jani Nikula
2025-09-18 17:38 ` Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 03/10] drm/{i915, xe}/fbdev: pass struct drm_device to intel_fbdev_fb_alloc() Jani Nikula
2025-09-18 17:39 ` [PATCH v2 03/10] drm/{i915,xe}/fbdev: " Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 04/10] drm/{i915, xe}/fbdev: deduplicate struct drm_mode_fb_cmd2 init Jani Nikula
2025-09-18 17:40 ` [PATCH v2 04/10] drm/{i915,xe}/fbdev: " Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 05/10] drm/i915/fbdev: abstract bo creation Jani Nikula
2025-09-18 17:42 ` Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 06/10] drm/xe/fbdev: " Jani Nikula
2025-09-18 17:42 ` Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 07/10] drm/{i915, xe}/fbdev: add intel_fbdev_fb_bo_destroy() Jani Nikula
2025-09-18 17:43 ` [PATCH v2 07/10] drm/{i915,xe}/fbdev: " Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 08/10] drm/{i915,xe}/fbdev: deduplicate fbdev creation Jani Nikula
2025-09-18 17:44 ` Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 09/10] drm/{i915, xe}/fbdev: pass struct drm_device to intel_fbdev_fb_fill_info() Jani Nikula
2025-09-18 17:45 ` [PATCH v2 09/10] drm/{i915,xe}/fbdev: " Ville Syrjälä
2025-09-18 8:41 ` [PATCH v2 10/10] drm/i915/fbdev: drop dependency on display in i915 specific code Jani Nikula
2025-09-18 17:50 ` Ville Syrjälä
2025-09-19 7:00 ` Jani Nikula
2025-09-18 8:59 ` ✓ CI.KUnit: success for drm/{i915,xe}/fbdev: refactor (rev2) Patchwork
2025-09-18 9:33 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-18 15:54 ` ✓ Xe.CI.Full: " 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=cover.1758184771.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