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: Re: [PATCH v2 2/4] serdev: add private data to serdev_device
Date: Mon, 09 Mar 2026 08:21:39 +1000	[thread overview]
Message-ID: <review-patch2-934ca1e6-dfee-411e-890a-083dcfc9f6b1@infradead.org> (raw)
In-Reply-To: <934ca1e6-dfee-411e-890a-083dcfc9f6b1@infradead.org>

Patch Review

```c
+ * @private_data Private data for the device driver.
  */
 struct serdev_device {
 	...
+	void *private_data;
 };
```

**Missing colon in kernel-doc**: The `@private_data` line is missing the colon separator used by all other fields. Should be `@private_data:`.

**Design concern**: `struct serdev_device` already has driver data via `dev_get_drvdata()`/`dev_set_drvdata()` on the embedded `struct device`. Adding a second `private_data` field is unusual. The commit message explains this is needed because the Rust abstraction uses `drvdata` for the driver type `T`, and needs a separate field for internal `PrivateData`. This is a C ABI change visible to all serdev users and should be discussed with the serdev maintainer (Rob Herring). Consider whether the Rust side could instead embed its `PrivateData` alongside the driver type in a wrapper struct stored in the standard `drvdata`, avoiding the C-side change entirely.

---

---
Generated by Claude Code Patch Reviewer

  parent reply	other threads:[~2026-03-08 22:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06 19:35 [PATCH v2 0/4] rust: add basic serial device bus abstractions Markus Probst
2026-03-06 19:35 ` [PATCH v2 1/4] rust: devres: return reference in `devres::register` Markus Probst
2026-03-08 22:21   ` Claude review: " Claude Code Review Bot
2026-03-06 19:35 ` [PATCH v2 2/4] serdev: add private data to serdev_device Markus Probst
2026-03-06 19:49   ` Randy Dunlap
2026-03-06 20:14     ` Markus Probst
2026-03-08 22:21     ` Claude Code Review Bot [this message]
2026-03-06 20:29   ` Danilo Krummrich
2026-03-06 19:35 ` [PATCH v2 3/4] rust: add basic serial device bus abstractions Markus Probst
2026-03-06 20:36   ` Markus Probst
2026-03-06 20:40   ` Danilo Krummrich
2026-03-06 20:46     ` Markus Probst
2026-03-08 22:21     ` Claude review: " Claude Code Review Bot
2026-03-06 19:35 ` [PATCH v2 4/4] samples: rust: add Rust serial device bus sample device driver Markus Probst
2026-03-08 22:21   ` Claude review: " Claude Code Review Bot
2026-03-08 22:21 ` Claude review: rust: add basic serial device bus abstractions 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-patch2-934ca1e6-dfee-411e-890a-083dcfc9f6b1@infradead.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