public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/i915/edp: Check supported link rates DPCD read
Date: Thu, 04 Jun 2026 16:24:48 +1000	[thread overview]
Message-ID: <review-overall-20260529145759.1640646-1-n.zhandarovich@fintech.ru> (raw)
In-Reply-To: <20260529145759.1640646-1-n.zhandarovich@fintech.ru>

Overall Series Review

Subject: drm/i915/edp: Check supported link rates DPCD read
Author: Nikita Zhandarovich <n.zhandarovich@fintech.ru>
Patches: 3
Reviewed: 2026-06-04T16:24:48.707404

---

This is a single-patch series (v2) that adds error checking to the `drm_dp_dpcd_read()` call in `intel_edp_set_sink_rates()`. The patch addresses a real static-analysis finding: the original code unconditionally parsed the `sink_rates[]` array even if the DPCD read failed, potentially using uninitialized stack data.

The fix is reasonable and follows the v2 feedback from Jani Nikula to use `drm_dp_dpcd_read_data()` instead of `drm_dp_dpcd_read()` and to avoid a goto. The approach of zeroing the array on failure is safe because the existing loop already treats a zero rate as a terminator (`if (rate == 0) break`), so `memset(sink_rates, 0, sizeof(sink_rates))` will cause the loop to immediately break and set `num_sink_rates = 0`, falling through to default handling.

**Verdict: The patch is correct and suitable for merging, with one minor observation below.**

---
Generated by Claude Code Patch Reviewer

  parent reply	other threads:[~2026-06-04  6:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29 14:57 [PATCH v2] drm/i915/edp: Check supported link rates DPCD read Nikita Zhandarovich
2026-05-29 15:16 ` Jani Nikula
2026-06-03  9:39   ` Jani Nikula
2026-06-04  6:24 ` Claude Code Review Bot [this message]
2026-06-04  6:24 ` Claude review: " Claude Code Review Bot
  -- strict thread matches above, loose matches on Subject: below --
2026-05-29 12:09 [PATCH] " Nikita Zhandarovich
2026-06-04  6:37 ` Claude review: " Claude Code Review Bot
2026-06-04  6:37 ` Claude Code Review Bot

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=review-overall-20260529145759.1640646-1-n.zhandarovich@fintech.ru \
    --to=claude-review@example.com \
    --cc=dri-devel-reviews@example.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