From: Jani Nikula <jani.nikula@intel.com>
To: "Kandpal, Suraj" <suraj.kandpal@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "Grzelak, Michal" <michal.grzelak@intel.com>
Subject: RE: [PATCH] drm/i915/ddi: add wrapper for calling ->get_buf_trans() hook
Date: Fri, 24 Apr 2026 11:28:54 +0300 [thread overview]
Message-ID: <00f5c612c22f8b626736003e889330cf2876447a@intel.com> (raw)
In-Reply-To: <DM3PPF208195D8D3C6C4E3E729D61D48F2DE32B2@DM3PPF208195D8D.namprd11.prod.outlook.com>
On Fri, 24 Apr 2026, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
>> Subject: [PATCH] drm/i915/ddi: add wrapper for calling ->get_buf_trans() hook
>>
>> Add intel_ddi_buf_trans_get() wrapper for calling the
>
> Nit: Could we name this intel_ddi_get_buf_trans() to keep the hook name and function name that calls this hook uniform
> But with or without this change
I put more value in having the function name prefix be the same as the
file name.
> Reviewed-by: Suraj Kandpal <suraj.kandpal@intel.com>
Thanks, pushed to drm-intel-next.
BR,
Jani.
>
>> encoder->get_buf_trans() hooks, allowing for a centralized place to
>> e.g. check for VBT overrides for the buf translations.
>>
>> Cc: Michał Grzelak <michal.grzelak@intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
--
Jani Nikula, Intel
prev parent reply other threads:[~2026-04-24 8:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 11:51 [PATCH] drm/i915/ddi: add wrapper for calling ->get_buf_trans() hook Jani Nikula
2026-04-15 11:58 ` ✓ CI.KUnit: success for " Patchwork
2026-04-15 12:46 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-15 14:49 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-24 2:52 ` [PATCH] " Kandpal, Suraj
2026-04-24 8:28 ` Jani Nikula [this message]
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=00f5c612c22f8b626736003e889330cf2876447a@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.grzelak@intel.com \
--cc=suraj.kandpal@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