From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/ttm/tests: fix lru_count ASSERT
Date: Sun, 12 Apr 2026 11:28:14 +1000 [thread overview]
Message-ID: <review-overall-20260409111032.72141-2-matthew.auld@intel.com> (raw)
In-Reply-To: <20260409111032.72141-2-matthew.auld@intel.com>
Overall Series Review
Subject: drm/ttm/tests: fix lru_count ASSERT
Author: Matthew Auld <matthew.auld@intel.com>
Patches: 2
Reviewed: 2026-04-12T11:28:14.294748
---
This is a single-patch fix for a logic bug in the TTM pool KUnit test. The fix is straightforward and correct: a double-negation in an assertion was causing the test to assert the opposite of what was intended. The commit message is clear, includes CI failure output demonstrating the problem, and has the appropriate `Fixes:` tag.
**Verdict: Looks good.**
---
Generated by Claude Code Patch Reviewer
prev parent reply other threads:[~2026-04-12 1:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 11:10 [PATCH] drm/ttm/tests: fix lru_count ASSERT Matthew Auld
2026-04-09 12:07 ` Knop, Ryszard
2026-04-09 12:18 ` [PATCH] " Christian König
2026-04-12 1:28 ` Claude review: " Claude Code Review Bot
2026-04-12 1:28 ` Claude Code Review Bot [this message]
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-20260409111032.72141-2-matthew.auld@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