From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/mediatek: dsi: Store driver data before invoking mipi_dsi_host_register
Date: Sun, 22 Mar 2026 03:36:31 +1000 [thread overview]
Message-ID: <review-overall-20260320153753.25450-1-l.scorcia@gmail.com> (raw)
In-Reply-To: <20260320153753.25450-1-l.scorcia@gmail.com>
Overall Series Review
Subject: drm/mediatek: dsi: Store driver data before invoking mipi_dsi_host_register
Author: Luca Leonardo Scorcia <l.scorcia@gmail.com>
Patches: 1
Reviewed: 2026-03-22T03:36:31.537150
---
This is a single-patch fix for a real NULL pointer dereference crash in the MediaTek DSI driver during probe. The analysis is correct and the fix is straightforward. The commit `e4732b590a77` moved `mipi_dsi_host_register` earlier in the probe sequence but left `platform_set_drvdata` after it, causing `dev_get_drvdata` in the `mtk_dsi_bind` callback path to return NULL.
The patch is well-motivated with a clear crash trace, has already been reviewed by the MediaTek DRM maintainers (CK Hu) and Collabora's Angelo Del Regno, and is on its v3 iteration.
**Verdict: Looks good. Ready to merge.**
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-03-21 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 15:37 [PATCH v3 RESEND] drm/mediatek: dsi: Store driver data before invoking mipi_dsi_host_register Luca Leonardo Scorcia
2026-03-21 17:36 ` Claude review: " Claude Code Review Bot
2026-03-21 17:36 ` Claude Code Review Bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-25 9:38 [PATCH v3] " Luca Leonardo Scorcia
2026-02-27 3:42 ` Claude review: " Claude Code Review Bot
2026-02-27 3:42 ` Claude Code Review Bot
2026-02-23 14:16 [PATCH v2] " Luca Leonardo Scorcia
2026-02-24 0:09 ` Claude review: " Claude Code Review Bot
2026-02-24 0:09 ` 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-overall-20260320153753.25450-1-l.scorcia@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