From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/xe: Handle PUNIT errors by requesting cold-reset recovery
Date: Mon, 25 May 2026 21:57:09 +1000 [thread overview]
Message-ID: <review-patch4-20260520113351.171119-11-mallesh.koujalagi@intel.com> (raw)
In-Reply-To: <20260520113351.171119-11-mallesh.koujalagi@intel.com>
Patch Review
The core change is correct:
```c
static void punit_error_handler(struct xe_device *xe)
{
xe_device_set_wedged_method(xe, DRM_WEDGE_RECOVERY_COLD_RESET);
xe_device_declare_wedged(xe);
}
```
This properly uses the wedge API (unlike the bypass in patch 1's PCI error handling path). The TODO comment it replaces is cleanly removed.
**Unnecessary includes:**
```c
+#include "xe_assert.h"
+#include "xe_device_types.h"
```
Neither `xe_assert.h` nor `xe_device_types.h` appear to be needed by the changes in this patch. `xe_device.h` (already included) transitively provides `xe_device_types.h`, and nothing in this diff uses `xe_assert`. These may have been added speculatively for patch 5, but each patch should only add headers it actually needs. If patch 5 needs them, add them there.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-25 11:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 11:33 [PATCH v6 0/5] Introduce cold reset recovery method Mallesh Koujalagi
2026-05-20 11:33 ` [PATCH v6 1/5] Introduce Xe Uncorrectable Error Handling Mallesh Koujalagi
2026-05-25 11:57 ` Claude review: " Claude Code Review Bot
2026-05-20 11:33 ` [PATCH v6 2/5] drm: Add DRM_WEDGE_RECOVERY_COLD_RESET recovery method Mallesh Koujalagi
2026-05-25 11:57 ` Claude review: " Claude Code Review Bot
2026-05-20 11:33 ` [PATCH v6 3/5] drm/doc: Document " Mallesh Koujalagi
2026-05-25 11:57 ` Claude review: " Claude Code Review Bot
2026-05-20 11:33 ` [PATCH v6 4/5] drm/xe: Handle PUNIT errors by requesting cold-reset recovery Mallesh Koujalagi
2026-05-25 11:57 ` Claude Code Review Bot [this message]
2026-05-20 11:33 ` [PATCH v6 5/5] drm/xe: Suppress Surprise Link Down on non-hotplug device Mallesh Koujalagi
2026-05-25 11:57 ` Claude review: " Claude Code Review Bot
2026-05-25 11:57 ` Claude review: Introduce cold reset recovery method Claude Code Review Bot
-- strict thread matches above, loose matches on Subject: below --
2026-05-12 13:26 [PATCH v5 0/5] " Mallesh Koujalagi
2026-05-12 13:26 ` [PATCH v5 4/5] drm/xe: Handle PUNIT errors by requesting cold-reset recovery Mallesh Koujalagi
2026-05-16 3:17 ` Claude review: " Claude Code Review Bot
2026-04-06 14:23 [PATCH v3 0/4] Introduce cold reset recovery method Mallesh Koujalagi
2026-04-06 14:23 ` [PATCH v3 4/4] drm/xe: Handle PUNIT errors by requesting cold-reset recovery Mallesh Koujalagi
2026-04-12 4:32 ` 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-patch4-20260520113351.171119-11-mallesh.koujalagi@intel.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