From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/imagination: Add missing rogue context reset reasons
Date: Wed, 25 Mar 2026 07:34:16 +1000 [thread overview]
Message-ID: <review-patch1-20260323-b4-firmware-context-reset-notification-handling-v3-1-1a66049a9a65@imgtec.com> (raw)
In-Reply-To: <20260323-b4-firmware-context-reset-notification-handling-v3-1-1a66049a9a65@imgtec.com>
Patch Review
**Verdict: Good.** This simply fills in the gap (values 6–11) in the `enum rogue_context_reset_reason` between `HARD_CONTEXT_SWITCH (5)` and `FW_WATCHDOG (12)`. The values and comments are clear and consistent with the existing style.
No issues found.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-03-24 21:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 18:31 [PATCH v3 0/3] drm/imagination: Firmware handling of context reset notification Alexandru Dadu
2026-03-23 18:31 ` [PATCH v3 1/3] drm/imagination: Add missing rogue context reset reasons Alexandru Dadu
2026-03-24 21:34 ` Claude Code Review Bot [this message]
2026-03-23 18:31 ` [PATCH v3 2/3] drm/imagination: Switch reset_reason fields from enum to u32 Alexandru Dadu
2026-03-24 21:34 ` Claude review: " Claude Code Review Bot
2026-03-23 18:31 ` [PATCH v3 3/3] drm/imagination: Implement handling of context reset notification Alexandru Dadu
2026-03-24 21:34 ` Claude review: " Claude Code Review Bot
2026-03-24 8:26 ` [PATCH v3 0/3] drm/imagination: Firmware " Matt Coster
2026-03-24 21:34 ` Claude review: " Claude Code Review Bot
-- strict thread matches above, loose matches on Subject: below --
2026-03-12 11:40 [PATCH v2 0/3] " Alexandru Dadu
2026-03-12 11:40 ` [PATCH v2 1/3] drm/imagination: Add missing rogue context reset reasons Alexandru Dadu
2026-03-13 4:16 ` 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-20260323-b4-firmware-context-reset-notification-handling-v3-1-1a66049a9a65@imgtec.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