From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/panel-edp: Add BOE NV153WUM-N42, CMN N153JCA-ELK, CSW MNF307QS3-2
Date: Sun, 22 Mar 2026 04:49:58 +1000 [thread overview]
Message-ID: <review-patch1-20260319050938.556235-1-alvin1.chen@lcfc.corp-partner.google.com> (raw)
In-Reply-To: <20260319050938.556235-1-alvin1.chen@lcfc.corp-partner.google.com>
Patch Review
**Critical: Malformed diff — double `+` prefix**
All three added lines use `++` instead of `+` as the diff addition marker:
```
++ EDP_PANEL_ENTRY('B', 'O', 'E', 0x0db3, &delay_200_500_e80, "NV153WUM-N42"),
++ EDP_PANEL_ENTRY('C', 'M', 'N', 0x156b, &delay_200_500_e80_d50, "N153JCA-ELK"),
++ EDP_PANEL_ENTRY('C', 'S', 'W', 0x1529, &delay_200_500_e80_d50, "MNF307QS3-2"),
```
This will cause `git am` / `patch` to fail. Each of these lines should have a single `+` prefix. This is likely why the patches could not be applied to the kernel tree.
**Delay structure choices:**
- **BOE 0x0db3**: Uses `&delay_200_500_e80`. Surrounding BOE entries use a mix of `delay_200_500_e50` and `delay_200_500_e80`, so this seems reasonable but there's no justification in the commit message for why `e80` was chosen over `e50`.
- **CMN 0x156b**: Uses `&delay_200_500_e80_d50`. The adjacent CMN entries (`0x1565` uses `delay_200_500_e80`, `0x162b` uses `delay_200_500_e80_d50`). The choice of `_d50` variant should be justified — was this determined from the panel datasheet?
- **CSW 0x1529**: Uses `&delay_200_500_e80_d50`. Adjacent CSW entries use various delays. Again, no justification provided.
**Panel ID verification from EDID:**
Checking the EDID data against the product codes:
- BOE EDID bytes 8-9: `09 e5` (manufacturer), bytes 10-11: `b3 0d` → product code 0x0db3. Matches.
- CMN EDID bytes 8-9: `0d ae` (manufacturer), bytes 10-11: `6b 15` → product code 0x156b. Matches.
- CSW EDID bytes 8-9: `0e 77` (manufacturer), bytes 10-11: `29 15` → product code 0x1529. Matches.
The panel IDs are correctly extracted from the EDIDs.
**Sorting:** The entries appear to be inserted in the correct sorted order by product code within each manufacturer section.
**Summary of issues:**
1. **Must fix:** The `++` prefix on all three added lines is a showstopper — the patch cannot be applied as-is. Resubmit with proper single-`+` diff markers.
2. **Nice to have:** The commit message should briefly justify the chosen delay structures (e.g., "delays chosen based on datasheet" or "reusing delays from similar panel model X").
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-03-21 18:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 5:09 [PATCH v3] drm/panel-edp: Add BOE NV153WUM-N42, CMN N153JCA-ELK, CSW MNF307QS3-2 Alvin1 Chen
2026-03-20 1:04 ` Doug Anderson
2026-03-21 14:03 ` kernel test robot
2026-03-21 16:38 ` Doug Anderson
2026-03-21 16:15 ` kernel test robot
2026-03-21 17:52 ` kernel test robot
2026-03-21 18:49 ` Claude Code Review Bot [this message]
2026-03-21 18:49 ` Claude review: " Claude Code Review Bot
-- strict thread matches above, loose matches on Subject: below --
2026-03-19 4:44 [PATCH v2] " Alvin1 Chen
2026-03-21 18:27 ` Claude review: " Claude Code Review Bot
2026-03-21 18:27 ` 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-20260319050938.556235-1-alvin1.chen@lcfc.corp-partner.google.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