From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm: verisilicon: DRM_VERISILICON_DC should depend on ARCH_THEAD
Date: Fri, 27 Feb 2026 12:27:47 +1000 [thread overview]
Message-ID: <review-patch1-fd65d4c53463e9579f59d7532ac6cce795d57aca.1772103393.git.geert+renesas@glider.be> (raw)
In-Reply-To: <fd65d4c53463e9579f59d7532ac6cce795d57aca.1772103393.git.geert+renesas@glider.be>
Patch Review
**Commit message:** Clear and well-written. Correctly explains the rationale (driver only supports DC8200 in TH1520), notes the Fixes tag, and mentions that the dependency can be relaxed later.
**Code change:**
```diff
- depends on RISCV || COMPILE_TEST
+ depends on ARCH_THEAD || COMPILE_TEST
```
This is correct. `ARCH_THEAD` is defined under `arch/riscv/Kconfig.socs` and already implies `RISCV`, so the architecture constraint is preserved while being more specific. The `COMPILE_TEST` alternative is properly kept so build-testing coverage is not lost.
The pattern matches what other T-HEAD peripheral drivers use throughout the tree. For example, `drivers/firmware/Kconfig:216` and `drivers/clk/thead/Kconfig:5` both have the identical `depends on ARCH_THEAD || COMPILE_TEST` construct.
**Fixes tag:** References `dbf21777caa8b8c8 ("drm: verisilicon: add a driver for Verisilicon display controllers")` which is appropriate — this is the commit that introduced the overly broad dependency.
**No issues found.**
Reviewed-by worthy as-is.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-02-27 2:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 11:00 [PATCH] drm: verisilicon: DRM_VERISILICON_DC should depend on ARCH_THEAD Geert Uytterhoeven
2026-02-26 15:36 ` Icenowy Zheng
2026-02-27 2:27 ` Claude Code Review Bot [this message]
2026-02-27 2:27 ` Claude review: " 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-patch1-fd65d4c53463e9579f59d7532ac6cce795d57aca.1772103393.git.geert+renesas@glider.be \
--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