From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/amdkfd: remove duplicate ttmp11 scheduling mode definitions
Date: Fri, 27 Feb 2026 14:54:14 +1000 [thread overview]
Message-ID: <review-overall-20260224-drm-amdkfd-ttmp11-sched-mode-v1-1-4254ff8952c4@redhat.com> (raw)
In-Reply-To: <20260224-drm-amdkfd-ttmp11-sched-mode-v1-1-4254ff8952c4@redhat.com>
Overall Series Review
Subject: drm/amdkfd: remove duplicate ttmp11 scheduling mode definitions
Author: Peter Colberg <pcolberg@redhat.com>
Patches: 1
Reviewed: 2026-02-27T14:54:14.464602
---
This is a single, straightforward cleanup patch. The original commit `bbcad5a8896b` introduced duplicate definitions of `TTMP11_SCHED_MODE_SHIFT`, `TTMP11_SCHED_MODE_SIZE`, and `TTMP11_SCHED_MODE_MASK` in `cwsr_trap_handler_gfx12.asm`. One copy was inside an `#if RELAXED_SCHEDULING_IN_TRAP` guard, the other was unconditional. Since all uses of these variables are within `#if RELAXED_SCHEDULING_IN_TRAP` blocks, the unconditional copy was unnecessary and the guarded copy was redundant.
The patch removes the first (guarded) copy and adds `#if RELAXED_SCHEDULING_IN_TRAP` / `#endif` guards around the second (previously unconditional) copy. This keeps the definitions grouped with the other `TTMP11_*` variables, which is the better location.
**Verdict: Looks good.** Clean, minimal, and correct.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-02-27 4:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 17:21 [PATCH] drm/amdkfd: remove duplicate ttmp11 scheduling mode definitions Peter Colberg
2026-02-27 4:54 ` Claude review: " Claude Code Review Bot
2026-02-27 4:54 ` Claude Code Review Bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-03 21:29 [PATCH RESEND] " Peter Colberg
2026-03-03 22:32 ` Claude review: " Claude Code Review Bot
2026-03-03 22:32 ` 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-20260224-drm-amdkfd-ttmp11-sched-mode-v1-1-4254ff8952c4@redhat.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