From: Jani Nikula <jani.nikula@linux.intel.com>
To: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
Subject: Re: [PATCH] drm/i915/display: take out dead code
Date: Tue, 19 Aug 2025 16:35:28 +0300 [thread overview]
Message-ID: <18cbef61b95915120e5c25ce96e3d426cede87ac@intel.com> (raw)
In-Reply-To: <20250819132526.18643-1-juhapekka.heikkila@gmail.com>
On Tue, 19 Aug 2025, Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com> wrote:
> if __waitfor timeout, ret will have -ETIMEDOUT. Then if condition
> was met, and read_ret will have error that's handled.
> Then if ret was zero, read_ret was zero ksv_ready must have value.
>
> Signed-off-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_hdcp.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_hdcp.c b/drivers/gpu/drm/i915/display/intel_hdcp.c
> index 42202c8bb066..2e34b625c80b 100644
> --- a/drivers/gpu/drm/i915/display/intel_hdcp.c
> +++ b/drivers/gpu/drm/i915/display/intel_hdcp.c
> @@ -334,8 +334,6 @@ static int intel_hdcp_poll_ksv_fifo(struct intel_digital_port *dig_port,
> return ret;
> if (read_ret)
> return read_ret;
> - if (!ksv_ready)
> - return -ETIMEDOUT;
>
> return 0;
> }
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-08-19 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 13:25 [PATCH] drm/i915/display: take out dead code Juha-Pekka Heikkila
2025-08-19 13:35 ` Jani Nikula [this message]
2025-08-19 14:39 ` ✓ i915.CI.BAT: success for " Patchwork
2025-08-19 18:35 ` ✗ i915.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=18cbef61b95915120e5c25ce96e3d426cede87ac@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=juhapekka.heikkila@gmail.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;
as well as URLs for NNTP newsgroup(s).