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: rust: Add ARef support for work items
Date: Wed, 25 Mar 2026 07:11:03 +1000	[thread overview]
Message-ID: <review-overall-20260323-aref-workitem-v3-0-f59729b812aa@collabora.com> (raw)
In-Reply-To: <20260323-aref-workitem-v3-0-f59729b812aa@collabora.com>

Overall Series Review

Subject: rust: Add ARef support for work items
Author: Daniel Almeida <daniel.almeida@collabora.com>
Patches: 7
Reviewed: 2026-03-25T07:11:03.971230

---

This is a well-structured 4-patch series that adds `ARef<T>` support for work items in the kernel's Rust workqueue subsystem, and then uses that support to allow `drm::Device<T>` to dispatch work items through to its driver-private data (`T::Data`). The series follows the established pattern from the existing `Arc<T>` and `Pin<KBox<T>>` implementations closely. The code is clean, the safety comments are thorough, and the series has already been reviewed by Alice Ryhl and acked by Danilo Krummrich.

The implementation is sound — `ARef::into_raw` / `ARef::from_raw` use `NonNull<T>` which aligns well with the work item lifecycle pattern of leaking a pointer on enqueue and reclaiming it in the `run` callback. The `drm::Device` dispatching approach (forwarding `HasWork`/`HasDelayedWork`/`WorkItem` implementations to `T::Data` via `container_of`) is a reasonable way to work around the orphan rule.

No blocking issues found. A few minor observations below.

---
Generated by Claude Code Patch Reviewer

      parent reply	other threads:[~2026-03-24 21:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 23:26 [PATCH v3 0/4] rust: Add ARef support for work items Daniel Almeida
2026-03-23 23:26 ` [PATCH v3 1/4] rust: workqueue: add support for ARef<T> Daniel Almeida
2026-03-24 11:00   ` Alice Ryhl
2026-03-24 21:11   ` Claude review: " Claude Code Review Bot
2026-03-23 23:27 ` [PATCH v3 2/4] rust: drm: dispatch work items to the private data Daniel Almeida
2026-03-24 21:11   ` Claude review: " Claude Code Review Bot
2026-03-23 23:27 ` [PATCH v3 3/4] rust: workqueue: add delayed work support for ARef<T> Daniel Almeida
2026-03-24 21:11   ` Claude review: " Claude Code Review Bot
2026-03-23 23:27 ` [PATCH v3 4/4] rust: drm: dispatch delayed work items to the private data Daniel Almeida
2026-03-24 21:11   ` Claude review: " Claude Code Review Bot
2026-03-24  8:20 ` [PATCH v3 0/4] rust: Add ARef support for work items Alice Ryhl
2026-03-24 21:11 ` 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-20260323-aref-workitem-v3-0-f59729b812aa@collabora.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