From: Jani Nikula <jani.nikula@linux.intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH 0/3] Remove Stubs in HDCP code
Date: Fri, 22 Sep 2023 12:29:48 +0300 [thread overview]
Message-ID: <87r0mqo8s3.fsf@intel.com> (raw)
In-Reply-To: <20230922082909.334085-1-suraj.kandpal@intel.com>
On Fri, 22 Sep 2023, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
> This patch series aims to remove stubs from code in HDCP code.
> Patches 1 & 2 are just added so no rebase issue is created later
> and for buildbility patch 3 is what we actually aim to merge.
> Patch 1 brings HDCP code in par with current i915 state (removes stub).
> Patch 2 is i915 refactor which has been already floated.
> (https://patchwork.freedesktop.org/series/123955/)
This should probably not be merged before the upstream change has been
merged, so a) we can be sure we don't need to rehash this, and b) we can
reference the upstream commit with git cherry-pick -x.
BR,
Jani.
> Patch 3 adds the definition of intel_hdcp_gsc_check_status in Xe.
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
>
> Suraj Kandpal (3):
> drm/i915/hdcp: Remove i915 check stubs
> drm/i915/hdcp: Move checks for gsc health status
> drm/xe/hdcp: Define intel_hdcp_gsc_check_status in Xe
>
> drivers/gpu/drm/i915/display/intel_hdcp.c | 13 +------------
> drivers/gpu/drm/i915/display/intel_hdcp_gsc.c | 14 ++++++++++++++
> drivers/gpu/drm/i915/display/intel_hdcp_gsc.h | 1 +
> drivers/gpu/drm/xe/display/xe_hdcp_gsc.c | 5 +++++
> 4 files changed, 21 insertions(+), 12 deletions(-)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-09-22 9:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 8:29 [Intel-xe] [PATCH 0/3] Remove Stubs in HDCP code Suraj Kandpal
2023-09-22 8:29 ` [Intel-xe] [PATCH 1/3] drm/i915/hdcp: Remove i915 check stubs Suraj Kandpal
2023-09-22 9:27 ` Jani Nikula
2023-09-22 10:14 ` Kandpal, Suraj
2023-09-22 10:38 ` [Intel-xe] [PATCH 1/3] fixup! FIXME: drm/i915: xe doesn't have gsc hdcp interface or something Suraj Kandpal
2023-10-09 8:52 ` Shankar, Uma
2023-10-09 8:58 ` Kandpal, Suraj
2023-10-09 9:16 ` Shankar, Uma
2023-09-22 8:29 ` [Intel-xe] [PATCH 2/3] drm/i915/hdcp: Move checks for gsc health status Suraj Kandpal
2023-09-22 8:29 ` [Intel-xe] [PATCH 3/3] drm/xe/hdcp: Define intel_hdcp_gsc_check_status in Xe Suraj Kandpal
2023-10-09 9:19 ` Shankar, Uma
2023-09-22 8:58 ` [Intel-xe] ✗ CI.Patch_applied: failure for Remove Stubs in HDCP code (rev2) Patchwork
2023-09-22 9:29 ` Jani Nikula [this message]
2023-09-22 10:13 ` [Intel-xe] [PATCH 0/3] Remove Stubs in HDCP code Kandpal, Suraj
2023-09-22 10:59 ` [Intel-xe] ✓ CI.Patch_applied: success for Remove Stubs in HDCP code (rev3) Patchwork
2023-09-22 10:59 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-09-22 11:00 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-09-22 11:07 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-22 11:07 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-22 11:09 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-09-22 11:42 ` [Intel-xe] ✓ CI.BAT: success " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-09-22 6:42 [Intel-xe] [PATCH 0/3] Remove Stubs in HDCP code Suraj Kandpal
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=87r0mqo8s3.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--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