From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/amd/display: Fix DDC register assignment type errors
Date: Wed, 25 Mar 2026 08:17:44 +1000 [thread overview]
Message-ID: <review-patch1-20260322095155.248283-1-guilhermeivob@gmail.com> (raw)
In-Reply-To: <20260322095155.248283-1-guilhermeivob@gmail.com>
Patch Review
**Correctness:** The change is correct. The parameter types are changed from the non-existent `struct ddc_shift` / `struct ddc_mask` to `struct ddc_sh_mask`, which matches:
- The actual struct definition in `ddc_regs.h:130`
- The `hw_ddc` struct fields in `hw_ddc.h:34-35` (`const struct ddc_sh_mask *shifts` / `*masks`)
- All callers across every DCN/DCE generation
```c
- const struct ddc_shift *shift,
- const struct ddc_mask *mask)
+ const struct ddc_sh_mask *shift,
+ const struct ddc_sh_mask *mask)
```
**Nit on commit message:** The commit message says "Fix invalid type assignments in ddc_sh_mask" which is slightly misleading — the fix is in the *function parameter declarations*, not in `ddc_sh_mask` itself. Something like "Fix parameter type mismatches in dcn_define_ddc_registers_common()" would be clearer. This is minor and not a blocker.
**Note:** The `hw_factory_dcn_ddc.h` file doesn't exist in the current drm-next tree I have access to, so the patch didn't apply. This likely depends on an earlier patch that introduced this file (and the bug along with it). The fix itself is valid regardless.
**Reviewed-by worthy:** Yes, this is a simple, correct type fix.
---
Generated by Claude Code Patch Reviewer
prev parent reply other threads:[~2026-03-24 22:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-22 9:51 [PATCH v2] drm/amd/display: Fix DDC register assignment type errors guilhermeivo
2026-03-24 22:17 ` Claude review: " Claude Code Review Bot
2026-03-24 22:17 ` 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-patch1-20260322095155.248283-1-guilhermeivob@gmail.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