From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/atomic: Allocate drm_private_state through a callback
Date: Fri, 27 Feb 2026 15:05:36 +1000 [thread overview]
Message-ID: <review-overall-20260224-drm-private-obj-reset-v5-0-5a72f8ec9934@kernel.org> (raw)
In-Reply-To: <20260224-drm-private-obj-reset-v5-0-5a72f8ec9934@kernel.org>
Overall Series Review
Subject: drm/atomic: Allocate drm_private_state through a callback
Author: Maxime Ripard <mripard@kernel.org>
Patches: 5
Reviewed: 2026-02-27T15:05:36.753298
---
**Series: drm/atomic: Allocate drm_private_state through a callback (v5)**
**Author: Maxime Ripard <mripard@kernel.org>**
This is a well-structured and logical cleanup series. It converts the three remaining `drm_private_obj` users (amdgpu, omapdrm, tegra) from the old pattern of externally allocating and passing state to `drm_atomic_private_obj_init()`, to the newer `atomic_create_state` callback pattern. Once all users are converted, patch 4 removes the now-unnecessary `state` parameter.
The series is sensible and follows the established direction for the DRM atomic API. The driver conversions are mechanical and straightforward. However, there is one significant issue: **none of the three driver patches check the return value of `drm_atomic_private_obj_init()`**, which can now fail when it internally calls `atomic_create_state`. There is also a cosmetic issue with the cover letter.
**Overall verdict**: Needs minor fixes for return value checking before merging.
---
---
Generated by Claude Code Patch Reviewer
prev parent reply other threads:[~2026-02-27 5:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 16:10 [PATCH v5 0/4] drm/atomic: Allocate drm_private_state through a callback Maxime Ripard
2026-02-24 16:10 ` [PATCH v5 1/4] drm/amdgpu: Switch private_obj initialization to atomic_create_state Maxime Ripard
2026-02-27 5:05 ` Claude review: " Claude Code Review Bot
2026-02-24 16:10 ` [PATCH v5 2/4] drm/omapdrm: " Maxime Ripard
2026-02-27 5:05 ` Claude review: " Claude Code Review Bot
2026-02-24 16:10 ` [PATCH v5 3/4] drm/tegra: " Maxime Ripard
2026-02-27 5:05 ` Claude review: " Claude Code Review Bot
2026-02-24 16:10 ` [PATCH v5 4/4] drm/atomic: Remove state argument to drm_atomic_private_obj_init Maxime Ripard
2026-02-27 5:05 ` Claude review: " Claude Code Review Bot
2026-02-27 5:05 ` Claude Code Review Bot [this message]
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-20260224-drm-private-obj-reset-v5-0-5a72f8ec9934@kernel.org \
--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