public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: Re: [PATCH] drm/amd/amdgpu: remove duplicated code in gfx_v11 and gfx_v12
Date: Tue, 05 May 2026 10:53:47 +1000	[thread overview]
Message-ID: <review-overall-dda47c3b-1303-4f10-b375-1f3eab032ee5@amd.com> (raw)
In-Reply-To: <dda47c3b-1303-4f10-b375-1f3eab032ee5@amd.com>

Overall Series Review

Subject: Re: [PATCH] drm/amd/amdgpu: remove duplicated code in gfx_v11 and gfx_v12
Author: =?UTF-8?Q?Christian_K=C3=B6nig?= <christian.koenig@amd.com>
Patches: 2
Reviewed: 2026-05-05T10:53:47.373114

---

This is a single-patch cleanup that consolidates identical `handle_priv_fault` implementations from `gfx_v11_0.c` and `gfx_v12_0.c` into a shared `amdgpu_gfx_handle_priv_fault()` in `amdgpu_gfx.c`. The consolidation is correct — I verified that the two original functions are byte-for-byte identical in the current tree. The mechanical transformation is clean.

However, there are a few issues:

1. **`Co-developed-by` tag ordering is wrong** — kernel documentation requires each `Co-developed-by` to be immediately followed by its corresponding `Signed-off-by`, with the submitter's `Signed-off-by` last.
2. **`BUG()` in the default case** — this is inherited from the original code, but consolidating into shared infrastructure is a good opportunity to fix it. `BUG()` in an interrupt handler will panic the kernel. The newer `gfx_v12_1` already uses `dev_dbg()` for this case instead.
3. **Incomplete consolidation** — `gfx_v10_0.c` has a nearly identical implementation (differing only in lacking the `disable_kq` guard), and `gfx_v12_1.c` has a related variant. At minimum, the commit message should acknowledge why these were excluded.
4. **Minor style issues** in the kernel-doc comment.

Verdict: Good idea, needs a v2 to fix the tag ordering and ideally address the `BUG()` concern.

---

---
Generated by Claude Code Patch Reviewer

  reply	other threads:[~2026-05-05  0:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29 17:36 [PATCH] drm/amd/amdgpu: remove duplicated code in gfx_v11 and gfx_v12 Ulisses Paixao
2026-04-30  6:21 ` Christian König
2026-05-05  0:53   ` Claude Code Review Bot [this message]
2026-05-05  0:53   ` 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-overall-dda47c3b-1303-4f10-b375-1f3eab032ee5@amd.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