Re: [PATCH v4 01/20] dt-bindings: phy: Add starfive,jh7110-inno-hdmi-phy
From: Joshua Peisach
Date: Thu Sep 17 2026 - 20:35:21 EST
On Thu Sep 17, 2026 at 2:51 AM EDT, Krzysztof Kozlowski wrote:
On Tue, Sep 15, 2026 at 05:32:09PM +0200, Michal Wilczynski wrote:I commented on v3 saying that I would test if I could. I don't just
Add the dt-binding for the StarFive JH7110 Innosilicon HDMI PHY.
This device is a child of the starfive,jh7110-hdmi-subsystem node. It
functions as both a PHY provider for the controller and as a clock
provider for the variable pixel clock (hdmi_pclk), which it generates
from its refoclk.
Reviewed-by: Joshua Peisach <jpeisach@xxxxxxxxxx>
While I appreciate other people looking at this, I don't think review
here applies. It was a blanket tag, given to the entire series, with
exception that it is from newbie, thus I want to ask: was this binding
REALLY reviewed by Joshua?
Are the rest of the patches actually reviewed or just "looks good to
me"? I see no comments from Joshua on v3, v2 and v1, which is usual sign
of doing review.
throw "Reviewed-by" on everything I look at.
If anything, I've been trying to be more honest in reviews, and only
review ones that I actually care about[1].
If reviewing patches isn't a good way for newbies to start getting
familiar with the kernel code (especially a NEW driver), then I don't
know what is.
And to be clear, I'm not using a LLM to review. I am using actual
intelligence. For the JH7110 PR specifically, I did actually go through
and review each commit, because I wanted to learn what was happening
and why. Actually, that's why I asked where the data sheet was[2].
So if you really want to, drop the Reviewed-by tag. And if it makes
you feel better, I'll leave the series alone.
-Josh
[1] I won't be reviewing PRs around devicetree since I'm not confident
(or frankly, interested) in it at this point. https://lore.kernel.org/all/DL94TU52KBMO.2HAKJMJXV2CPE@xxxxxxxxxx/
[2] Michal giving me the hardware info:
https://lore.kernel.org/all/071901ef-57f3-456f-af5b-a8c99a0a7dd3@xxxxxxxxxxx/