From: Jani Nikula <jani.nikula@linux.intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/3] drm/i915/hdcp: Rename HCDP 1.4 enablement function
Date: Thu, 26 Oct 2023 15:36:05 +0300 [thread overview]
Message-ID: <87ttqd7e8a.fsf@intel.com> (raw)
In-Reply-To: <20231026121139.987437-2-suraj.kandpal@intel.com>
On Thu, 26 Oct 2023, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
> Rename hdcp 1.4 enablement function from _intel_hdcp_enable to
> intel_hdcp1_enable to better represent what version of hdcp is
> being enabled
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-10-26 12:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 12:11 [Intel-gfx] [PATCH 0/3] drm/i915/hdcp: Additional conditions to enable hdcp Suraj Kandpal
2023-10-26 12:11 ` [Intel-gfx] [PATCH 1/3] drm/i915/hdcp: Rename HCDP 1.4 enablement function Suraj Kandpal
2023-10-26 12:36 ` Jani Nikula [this message]
2023-10-26 12:11 ` [Intel-gfx] [PATCH 2/3] drm/i915/hdcp: Convert intel_hdcp_enable to a blanket function Suraj Kandpal
2023-10-26 12:36 ` Jani Nikula
2023-10-26 12:11 ` [Intel-gfx] [PATCH 3/3] drm/i915/hdcp: Add more conditions to enable hdcp Suraj Kandpal
2023-10-27 5:58 ` Nautiyal, Ankit K
2023-10-27 3:35 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/hdcp: Additional conditions to enable hdcp (rev4) Patchwork
2023-10-27 3:47 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-10-28 10:03 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-10-30 6:12 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2023-10-31 11:04 ` [Intel-gfx] [PATCH 0/3] drm/i915/hdcp: Additional conditions to enable hdcp Nautiyal, Ankit K
-- strict thread matches above, loose matches on Subject: below --
2023-10-26 9:36 Suraj Kandpal
2023-10-26 9:36 ` [Intel-gfx] [PATCH 1/3] drm/i915/hdcp: Rename HCDP 1.4 enablement function 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=87ttqd7e8a.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@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