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>
Subject: RE: [PATCH 1/2] drm/i915/hdcp: move i915 specific HDCP GSC implementation to i915
Date: Fri, 28 Nov 2025 11:27:54 +0200 [thread overview]
Message-ID: <d0e81ef460c5ab25b053f38cfa0c3b77f797efd5@intel.com> (raw)
In-Reply-To: <DM3PPF208195D8D6748F2A492BB93672716E3DCA@DM3PPF208195D8D.namprd11.prod.outlook.com>
On Fri, 28 Nov 2025, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
>> Subject: [PATCH 1/2] drm/i915/hdcp: move i915 specific HDCP GSC
>> implementation to i915
>>
>> The HDCP GSC implementation is different for both i915 and xe. Move the
>> i915 specific implementation from display to i915 core.
>>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> LGTM,
> Reviewed-by: Suraj Kandpal <suraj.kandpal@intel.com>
Thanks, series pushed to din.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-11-28 9:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 17:17 [PATCH 0/2] drm/i915/hdcp: call HDCP GSC hook via parent interface Jani Nikula
2025-11-25 17:17 ` [PATCH 1/2] drm/i915/hdcp: move i915 specific HDCP GSC implementation to i915 Jani Nikula
2025-11-28 5:57 ` Kandpal, Suraj
2025-11-28 9:27 ` Jani Nikula [this message]
2025-11-25 17:17 ` [PATCH 2/2] drm/{i915, xe}/hdcp: use parent interface for HDCP GSC calls Jani Nikula
2025-11-28 6:02 ` Kandpal, Suraj
2025-11-26 2:23 ` ✗ CI.checkpatch: warning for drm/i915/hdcp: call HDCP GSC hook via parent interface Patchwork
2025-11-26 2:24 ` ✓ CI.KUnit: success " Patchwork
2025-11-26 3:12 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-26 5:57 ` ✗ Xe.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=d0e81ef460c5ab25b053f38cfa0c3b77f797efd5@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--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