From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/tests: Mark slow tests as slow
Date: Fri, 27 Feb 2026 15:13:20 +1000 [thread overview]
Message-ID: <review-overall-20260224110310.1854608-1-mripard@kernel.org> (raw)
In-Reply-To: <20260224110310.1854608-1-mripard@kernel.org>
Overall Series Review
Subject: drm/tests: Mark slow tests as slow
Author: Maxime Ripard <mripard@kernel.org>
Patches: 13
Reviewed: 2026-02-27T15:13:20.236229
---
This is a single, straightforward patch from Maxime Ripard that marks three DRM KUnit tests as slow using the `KUNIT_CASE_SLOW()` macro. The change is correct, well-scoped, and follows established KUnit conventions. The commit message is clear and concise.
The `KUNIT_CASE_SLOW` macro (defined in `include/kunit/test.h:187`) sets the `attr.speed` to `KUNIT_SPEED_SLOW`, which allows test runners to filter out slow tests (those exceeding the 1-second threshold) for faster iteration during development.
No issues found. This is a good cleanup patch.
---
Generated by Claude Code Patch Reviewer
prev parent reply other threads:[~2026-02-27 5:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 11:03 [PATCH] drm/tests: Mark slow tests as slow Maxime Ripard
2026-02-24 11:12 ` Thomas Zimmermann
2026-02-24 11:43 ` Danilo Krummrich
2026-02-24 12:29 ` Tvrtko Ursulin
2026-02-24 12:44 ` Philipp Stanner
2026-02-24 12:49 ` Tvrtko Ursulin
2026-02-26 10:56 ` Maxime Ripard
2026-02-26 12:42 ` Tvrtko Ursulin
2026-02-26 12:48 ` Philipp Stanner
2026-02-26 13:02 ` Tvrtko Ursulin
2026-02-26 13:17 ` Philipp Stanner
2026-02-26 13:23 ` Tvrtko Ursulin
2026-02-24 13:07 ` Arunpravin Paneer Selvam
2026-02-27 5:13 ` Claude review: " Claude Code Review Bot
2026-02-27 5:13 ` 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-20260224110310.1854608-1-mripard@kernel.org \
--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