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/atomic: duplicate state of all colorops
Date: Wed, 27 May 2026 14:45:25 +1000	[thread overview]
Message-ID: <review-patch2-20260526142940.504911-3-mwen@igalia.com> (raw)
In-Reply-To: <20260526142940.504911-3-mwen@igalia.com>

Patch Review

**Purpose:** In `drm_atomic_helper_duplicate_state()`, remove the `if (plane_state->color_pipeline)` guard so that **all** colorops are snapshotted regardless of whether a pipeline is currently active. This ensures colorop settings persist across deactivation/reactivation.

**The change is straightforward and correct:**

```c
-       if (plane_state->color_pipeline) {
-           err = drm_atomic_add_affected_colorops(state, plane);
-           if (err)
-               goto free;
-       }
-
+       err = drm_atomic_add_affected_colorops(state, plane);
+       if (err)
+           goto free;
```

**Minor concern — interaction with Patch 1:**  Patch 1 introduces `drm_atomic_add_pipeline_colorops()` for use in `drm_atomic_add_affected_planes()` (which only adds active/transitioning colorops), while this patch keeps `drm_atomic_add_affected_colorops()` here (which adds all colorops on the plane). The two functions serve legitimately different purposes, but having two similarly-named functions with different semantics could be confusing. A comment in the code or in the commit message acknowledging this intentional distinction would help.

**No bugs found.** The change correctly ensures persistence of colorop state across pipeline deactivation.

---

---
Generated by Claude Code Patch Reviewer

  reply	other threads:[~2026-05-27  4:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26 14:17 [PATCH 0/3] don't allow changes to inactive colorops Melissa Wen
2026-05-26 14:17 ` [PATCH 1/3] drm/atomic: only add states of active or transient active colorops Melissa Wen
2026-05-26 23:02   ` Alex Hung
2026-05-27  4:45   ` Claude review: " Claude Code Review Bot
2026-05-26 14:17 ` [PATCH 2/3] drm/atomic: duplicate state of all colorops Melissa Wen
2026-05-27  4:45   ` Claude Code Review Bot [this message]
2026-05-26 14:17 ` [PATCH 3/3] drm/atomic: reject colorop update from inactive color pipeline Melissa Wen
2026-05-26 23:04   ` Alex Hung
2026-05-27  4:45   ` Claude review: " Claude Code Review Bot
2026-05-27  4:45 ` Claude review: don't allow changes to inactive colorops 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-patch2-20260526142940.504911-3-mwen@igalia.com \
    --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