From: Jani Nikula <jani.nikula@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: uma.shankar@intel.com, ankit.k.nautiyal@intel.com,
Suraj Kandpal <suraj.kandpal@intel.com>
Subject: Re: [PATCH 0/2] HDCP intel_display refactors
Date: Wed, 11 Sep 2024 16:56:10 +0300 [thread overview]
Message-ID: <874j6mjnut.fsf@intel.com> (raw)
In-Reply-To: <20240911090540.643155-1-suraj.kandpal@intel.com>
On Wed, 11 Sep 2024, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
> Refactors related to intel_hdcp/xe_hdcp in which we replace
> drm_i915_private usage with intel_display wherever possible for
> the ongoing efforts to try use intel_display structure more.
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Yay!
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
>
> Suraj Kandpal (2):
> drm/i915/hdcp: Move to using intel_display in intel_hdcp
> drm/i915/hdcp: Use intel_display in hdcp_gsc
>
> drivers/gpu/drm/i915/display/intel_hdcp.c | 689 +++++++++---------
> drivers/gpu/drm/i915/display/intel_hdcp_gsc.c | 40 +-
> drivers/gpu/drm/i915/display/intel_hdcp_gsc.h | 9 +-
> .../drm/i915/display/intel_hdcp_gsc_message.c | 44 +-
> .../drm/i915/display/intel_hdcp_gsc_message.h | 3 +-
> drivers/gpu/drm/xe/display/xe_hdcp_gsc.c | 44 +-
> 6 files changed, 422 insertions(+), 407 deletions(-)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-09-11 13:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 9:05 [PATCH 0/2] HDCP intel_display refactors Suraj Kandpal
2024-09-11 9:05 ` [PATCH 1/2] drm/i915/hdcp: Move to using intel_display in intel_hdcp Suraj Kandpal
2024-09-11 9:05 ` [PATCH 2/2] drm/i915/hdcp: Use intel_display in hdcp_gsc Suraj Kandpal
2024-09-11 9:14 ` ✓ CI.Patch_applied: success for HDCP intel_display refactors (rev2) Patchwork
2024-09-11 9:14 ` ✓ CI.checkpatch: " Patchwork
2024-09-11 9:15 ` ✓ CI.KUnit: " Patchwork
2024-09-11 9:27 ` ✓ CI.Build: " Patchwork
2024-09-11 9:30 ` ✓ CI.Hooks: " Patchwork
2024-09-11 9:31 ` ✗ CI.checksparse: warning " Patchwork
2024-09-11 10:20 ` ✗ CI.BAT: failure " Patchwork
2024-09-11 11:26 ` ✗ CI.FULL: " Patchwork
2024-09-11 13:56 ` Jani Nikula [this message]
2024-09-11 18:07 ` ✗ Fi.CI.BUILD: warning " Patchwork
2024-09-11 18:07 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-09-11 18:30 ` ✓ Fi.CI.BAT: success " Patchwork
2024-09-11 23:53 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-09-12 10:24 ` ✓ Fi.CI.IGT: success " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-09-10 7:47 [PATCH 0/2] HDCP intel_display refactors 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=874j6mjnut.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=suraj.kandpal@intel.com \
--cc=uma.shankar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.