From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: accel/ivpu: Test for imported buffers with drm_gem_is_imported()
Date: Tue, 10 Mar 2026 12:33:19 +1000 [thread overview]
Message-ID: <review-patch1-20260309092755.3165130-1-karol.wachowski@linux.intel.com> (raw)
In-Reply-To: <20260309092755.3165130-1-karol.wachowski@linux.intel.com>
Patch Review
**Correctness:** The two changes are semantically identical to the code they replace. `drm_gem_is_imported()` (defined at `include/drm/drm_gem.h:646`) is simply `return !!obj->import_attach`, so:
1. `!bo->base.base.import_attach` → `!drm_gem_is_imported(&bo->base.base)` — equivalent, since `!` on a pointer is the same as `!` on `!!pointer`.
2. `bo->base.base.import_attach` → `drm_gem_is_imported(&bo->base.base)` — equivalent truthiness test.
**Consistency with existing codebase:** The ivpu driver already uses `drm_gem_is_imported()` in three other places in the same file (`ivpu_gem.c:34`, `ivpu_gem.c:317`, `ivpu_gem.c:552` on drm-next), so these two call sites were stragglers. This patch brings full consistency.
**Minor note:** In the second hunk at `ivpu_bo_unbind_locked`, the very next line still uses `bo->base.base.import_attach` directly:
```c
if (drm_gem_is_imported(&bo->base.base)) {
dma_buf_unmap_attachment(bo->base.base.import_attach,
bo->base.sgt, DMA_BIDIRECTIONAL);
```
This is correct — `dma_buf_unmap_attachment()` needs the actual `import_attach` pointer as a value, not a boolean test, so there's no accessor to replace there.
**Verdict:** Clean, correct, minimal patch. No concerns.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-03-10 2:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 9:27 [PATCH] accel/ivpu: Test for imported buffers with drm_gem_is_imported() Karol Wachowski
2026-03-09 9:39 ` Thomas Zimmermann
2026-03-09 9:50 ` Karol Wachowski
2026-03-10 2:33 ` Claude Code Review Bot [this message]
2026-03-10 2:33 ` 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-patch1-20260309092755.3165130-1-karol.wachowski@linux.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