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: drm/ttm/tests: Fix build failure on PREEMPT_RT
Date: Thu, 05 Mar 2026 13:40:45 +1000	[thread overview]
Message-ID: <review-overall-20260304085616.1216961-1-dev@lankhorst.se> (raw)
In-Reply-To: <20260304085616.1216961-1-dev@lankhorst.se>

Overall Series Review

Subject: drm/ttm/tests: Fix build failure on PREEMPT_RT
Author: Maarten Lankhorst <dev@lankhorst.se>
Patches: 3
Reviewed: 2026-03-05T13:40:45.267716

---

This is a single-patch fix for a compile error in TTM kunit tests when `CONFIG_PREEMPT_RT` is enabled. On PREEMPT_RT, `struct mutex` is replaced by `struct rt_mutex`, so directly accessing `bo->base.resv->lock.base` as a `mutex` fails to compile. The fix correctly switches to the proper `dma_resv_lock()`/`dma_resv_unlock()` API instead of reaching into ww_mutex internals. This is a clean, straightforward fix.

**Verdict: Looks good.**

---
Generated by Claude Code Patch Reviewer

  parent reply	other threads:[~2026-03-05  3:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04  8:56 [PATCH v2] drm/ttm/tests: Fix build failure on PREEMPT_RT Maarten Lankhorst
2026-03-04  8:58 ` Hogander, Jouni
2026-03-04  9:25   ` Maarten Lankhorst
2026-03-05  3:40 ` Claude review: " Claude Code Review Bot
2026-03-05  3:40 ` Claude Code Review Bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-02-26 15:12 [PATCH] " Maarten Lankhorst
2026-02-27  1:52 ` Claude review: " Claude Code Review Bot
2026-02-27  1:52 ` 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-20260304085616.1216961-1-dev@lankhorst.se \
    --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