intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [RESEND 0/4] drm/{i915,xe}/dsb: refactor DSB buffer allocation
Date: Wed, 22 Oct 2025 18:36:34 +0300	[thread overview]
Message-ID: <cover.1761147363.git.jani.nikula@intel.com> (raw)

Resend of [1].

[1] https://lore.kernel.org/r/cover.1758021803.git.jani.nikula@intel.com

Jani Nikula (4):
  drm/{i915,xe}/dsb: make {intel,xe}_dsb_buffer.c independent of display
  drm/{i915,xe}/dsb: allocate struct intel_dsb_buffer dynamically
  drm/{i915,xe}/dsb: make struct intel_dsb_buffer opaque
  drm/xe/dsb: drop the unnecessary struct i915_vma

 drivers/gpu/drm/i915/display/intel_dsb.c      | 42 +++++++++-------
 .../gpu/drm/i915/display/intel_dsb_buffer.c   | 43 ++++++++++++----
 .../gpu/drm/i915/display/intel_dsb_buffer.h   | 13 ++---
 drivers/gpu/drm/xe/display/xe_dsb_buffer.c    | 49 +++++++++++--------
 4 files changed, 88 insertions(+), 59 deletions(-)

-- 
2.47.3


             reply	other threads:[~2025-10-22 15:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22 15:36 Jani Nikula [this message]
2025-10-22 15:36 ` [RESEND 1/4] drm/{i915, xe}/dsb: make {intel, xe}_dsb_buffer.c independent of display Jani Nikula
2025-10-22 15:36 ` [RESEND 2/4] drm/{i915, xe}/dsb: allocate struct intel_dsb_buffer dynamically Jani Nikula
2025-10-22 15:36 ` [RESEND 3/4] drm/{i915,xe}/dsb: make struct intel_dsb_buffer opaque Jani Nikula
2025-10-22 15:36 ` [RESEND 4/4] drm/xe/dsb: drop the unnecessary struct i915_vma Jani Nikula
2025-10-22 23:18 ` ✓ i915.CI.BAT: success for drm/{i915,xe}/dsb: refactor DSB buffer allocation (rev2) Patchwork
2025-10-23  7:19 ` ✗ i915.CI.Full: 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=cover.1761147363.git.jani.nikula@intel.com \
    --to=jani.nikula@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 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).