public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Michał Grzelak" <michal.grzelak@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2 2/2] drm/{i915, xe}/dsb: move DSB buffer to parent interface
Date: Wed, 21 Jan 2026 00:04:03 +0100 (CET)	[thread overview]
Message-ID: <fa3f1073-b24c-9b2f-85a9-fd0aba801069@intel.com> (raw)
In-Reply-To: <df117c862a6d34dae340e4a85c2482b4e29c8884.1768923917.git.jani.nikula@intel.com>

[-- Attachment #1: Type: text/plain, Size: 800 bytes --]

On Tue, 20 Jan 2026, Jani Nikula wrote:
> Move the DSB buffer handling to the display parent interface, making
> display more independent of i915 and xe driver implementations.
>
> Since the DSB parent interface is only called from intel_dsb.c, add the
> wrappers there with smaller visibility instead of the usual
> intel_parent.[ch], and using struct intel_dsb as the context parameter
> for convenience.
>
> Unfortunately, memset() being a macro in linux/fortify-string.h, we
> can't use that as the function pointer name. dsb->memset() would be
> using the macro and leading to build failures. Therefore, use .fill()
> for the memset() functionality.
>
> v2: s/memset/fill/
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>

Reviewed-by: Michał Grzelak <michal.grzelak@intel.com>

BR,
Michał

  reply	other threads:[~2026-01-20 23:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 15:45 [PATCH v2 0/2] drm/{i915, xe}/dsb: move DSB buffer calls to parent interface Jani Nikula
2026-01-20 15:45 ` [PATCH v2 1/2] drm/i915/dsb: move i915 specific DSB buffer implementation to i915 Jani Nikula
2026-01-20 23:03   ` Michał Grzelak
2026-01-20 15:45 ` [PATCH v2 2/2] drm/{i915, xe}/dsb: move DSB buffer to parent interface Jani Nikula
2026-01-20 23:04   ` Michał Grzelak [this message]
2026-01-20 15:51 ` ✗ CI.checkpatch: warning for drm/{i915, xe}/dsb: move DSB buffer calls to parent interface (rev2) Patchwork
2026-01-20 15:53 ` ✓ CI.KUnit: success " Patchwork
2026-01-20 16:41 ` ✓ Xe.CI.BAT: " Patchwork
2026-01-20 21:29 ` ✓ 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=fa3f1073-b24c-9b2f-85a9-fd0aba801069@intel.com \
    --to=michal.grzelak@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox