Claude review: rust: drm: dispatch work items to the private data

[Claude Code Review Bot <claude-review@example.com>]

Patch Review

This patch implements `WorkItem` and `HasWork` for `Device<T>` to forward to `T::Data`.

**The `HasWork` implementation:**

```rust
unsafe impl<T, const ID: u64> HasWork<Device<T>, ID> for Device<T>
where
    T: drm::Driver,
    T::Data: HasWork<Device<T>, ID>,
{
    unsafe fn raw_get_work(ptr: *mut Self) -> *mut Work<Device<T>, ID> {
        let data_ptr = unsafe { &raw mut (*ptr).data };
        unsafe { T::Data::raw_get_work(data_ptr) }
    }
```

There's a subtle type issue worth noting: `T::Data::raw_get_work(data_ptr)` — the bound is `T::Data: HasWork<Device<T>, ID>`, so `raw_get_work` expects `*mut T::Data` (since `HasWork::raw_get_work` takes `*mut Self` where `Self = T::Data`). The `data_ptr` is `*mut T::Data` from `&raw mut (*ptr).data`, so this is correct.

The `work_container_of` does:

```rust
unsafe fn work_container_of(ptr: *mut Work<Device<T>, ID>) -> *mut Self {
    let data_ptr = unsafe { T::Data::work_container_of(ptr) };
    unsafe { crate::container_of!(data_ptr, Self, data) }
}
```

This correctly goes from `Work` → `T::Data` → `Device<T>` via `container_of`. Since `Device<T>` is `#[repr(C)]` with `data` as the second field, the `container_of` is valid.

**The `WorkItem` implementation:**

```rust
impl<T, const ID: u64> WorkItem<ID> for Device<T>
where
    T: drm::Driver,
    T::Data: WorkItem<ID, Pointer = ARef<Device<T>>>,
    T::Data: HasWork<Device<T>, ID>,
{
    type Pointer = ARef<Device<T>>;

    fn run(ptr: ARef<Device<T>>) {
        T::Data::run(ptr);
    }
}
```

This requires `T::Data: WorkItem<ID, Pointer = ARef<Device<T>>>`. This is the key constraint — the driver's data type must declare its work item pointer as `ARef<Device<T>>`, not `ARef<T::Data>`. This makes sense given the orphan rule motivation and is clearly documented in the commit message.

Looks correct.

---
Generated by Claude Code Patch Reviewer