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/bridge: aux: Add drm_aux_bridge_register_from_node()
Date: Thu, 05 Mar 2026 13:37:59 +1000	[thread overview]
Message-ID: <review-patch2-20260304094152.92-3-kernel@airkyi.com> (raw)
In-Reply-To: <20260304094152.92-3-kernel@airkyi.com>

Patch Review

Clean refactoring. The existing `drm_aux_bridge_register()` becomes a thin wrapper.

**Issue (minor): Doc comment on original function was modified incorrectly.** The `@np` parameter was added to the doc comment for `drm_aux_bridge_register()` before the function was renamed:

```c
/**
 * drm_aux_bridge_register - Create a simple bridge device to link the chain
 * @parent: device instance providing this bridge
 * @np: device node pointer corresponding to this bridge instance
```

But the function being documented is now `drm_aux_bridge_register_from_node()`, so this is technically fine, but the description text ("Create a simple bridge device to link the chain") doesn't mention the `np` override behavior. A note in the description about specifying a custom of_node would help.

No functional concerns. Reviewed-by from Neil Armstrong.

---
Generated by Claude Code Patch Reviewer

  reply	other threads:[~2026-03-05  3:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04  9:41 [PATCH v15 0/9] Add Type-C DP support for RK3399 EVB IND board Chaoyi Chen
2026-03-04  9:41 ` [PATCH v15 1/9] drm/bridge: Implement generic USB Type-C DP HPD bridge Chaoyi Chen
2026-03-05  3:37   ` Claude review: " Claude Code Review Bot
2026-03-04  9:41 ` [PATCH v15 2/9] drm/bridge: aux: Add drm_aux_bridge_register_from_node() Chaoyi Chen
2026-03-05  3:37   ` Claude Code Review Bot [this message]
2026-03-04  9:41 ` [PATCH v15 3/9] dt-bindings: phy: rockchip: rk3399-typec-phy: Support mode-switch Chaoyi Chen
2026-03-05  3:38   ` Claude review: " Claude Code Review Bot
2026-03-04  9:41 ` [PATCH v15 4/9] phy: rockchip: phy-rockchip-typec: Add typec_mux/typec_switch support Chaoyi Chen
2026-03-05  3:38   ` Claude review: " Claude Code Review Bot
2026-03-04  9:41 ` [PATCH v15 5/9] phy: rockchip: phy-rockchip-typec: Add DRM AUX bridge Chaoyi Chen
2026-03-05  3:38   ` Claude review: " Claude Code Review Bot
2026-03-04  9:41 ` [PATCH v15 6/9] drm/rockchip: cdn-dp: Support handle lane info without extcon Chaoyi Chen
2026-03-05  3:38   ` Claude review: " Claude Code Review Bot
2026-03-04  9:41 ` [PATCH v15 7/9] drm/rockchip: cdn-dp: Add multiple bridges to support PHY port selection Chaoyi Chen
2026-03-05  3:38   ` Claude review: " Claude Code Review Bot
2026-03-04  9:41 ` [PATCH v15 8/9] arm64: dts: rockchip: Add missing dp_out port for RK3399 CDN-DP Chaoyi Chen
2026-03-05  3:38   ` Claude review: " Claude Code Review Bot
2026-03-04  9:41 ` [PATCH v15 9/9] arm64: dts: rockchip: rk3399-evb-ind: Add support for DisplayPort Chaoyi Chen
2026-03-05  3:38   ` Claude review: " Claude Code Review Bot
2026-03-05  3:37 ` Claude review: Add Type-C DP support for RK3399 EVB IND board 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-20260304094152.92-3-kernel@airkyi.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