From mboxrd@z Thu Jan 1 00:00:00 1970 From: Claude Code Review Bot To: dri-devel-reviews@example.com Subject: Claude review: drm/bridge: handle refcounting for bridge-only callers of drm_of_find_panel_or_bridge() Date: Sat, 16 May 2026 15:02:22 +1000 Message-ID: In-Reply-To: <20260511-drm-bridge-alloc-getput-panel_or_bridge-v6-0-f61c9e498b3f@bootlin.com> References: <20260511-drm-bridge-alloc-getput-panel_or_bridge-v6-0-f61c9e498b3f@bootlin.com> X-Mailer: Claude Code Patch Reviewer Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Overall Series Review Subject: drm/bridge: handle refcounting for bridge-only callers of drm_of_f= ind_panel_or_bridge() Author: Luca Ceresoli Patches: 13 Reviewed: 2026-05-16T15:02:22.126708 --- This is a well-structured, incremental series that continues Luca Ceresoli'= s long-running work to add proper refcounting to DRM bridges. The series in= troduces `of_drm_get_bridge_by_endpoint()` as a refcount-aware replacement = for bridge-only calls to the deprecated `drm_of_find_panel_or_bridge()`, co= nverts all bridge-only callers, and then forbids that usage pattern going f= orward. The approach is sound: the new API is simpler (returns the bridge directly = instead of via double-pointer), safer (refcounted), and each driver convers= ion correctly handles the lifecycle of the returned bridge =E2=80=94 either= via the auto-put `bridge.next_bridge` field, explicit `drm_bridge_put()`, = or the `__free(drm_bridge_put)` cleanup annotation. All patches are already reviewed/acked except patches 3 and 4. The series i= s at v6, with the main changes across versions being error handling improve= ments. The code quality is high and the pattern is consistent. **No blocking issues found.** A couple of very minor nits below. --- Generated by Claude Code Patch Reviewer