From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/gpusvm: Drop redundant @flags.* kernel-doc on struct drm_gpusvm_pages
Date: Tue, 05 May 2026 09:11:20 +1000 [thread overview]
Message-ID: <review-patch1-20260501175956.4054088-1-shuicheng.lin@intel.com> (raw)
In-Reply-To: <20260501175956.4054088-1-shuicheng.lin@intel.com>
Patch Review
**Correctness:** The change is correct. Comparing with the kernel tree, `drm_gpusvm_notifier` (line 96-106) uses an anonymous `struct { u32 removed : 1; } flags;` where dotted `@flags.removed` notation *is* appropriate. But `drm_gpusvm_pages` (line 147-152) uses the named type `struct drm_gpusvm_pages_flags flags;`, which the kernel-doc parser does not flatten — so the `@flags.*` entries are indeed excess members that trigger warnings.
**The replacement line:**
```
* @flags: Flags for the range; see &struct drm_gpusvm_pages_flags
```
This correctly uses kernel-doc's `&struct` cross-reference syntax and provides a pointer to the canonical documentation.
**Minor observations:**
1. The patch context lines include `@state` and `@state_offset` fields that don't exist in the current drm-next tree, confirming this targets drm-misc (as stated in the v2 changelog). This is fine — the patch will apply cleanly on its intended base.
2. The commit message is well-written: it explains the root cause (named vs anonymous struct semantics in kernel-doc), quotes the specific warnings, and states "No functional change."
3. The `Assisted-by: Claude:claude-opus-4.6` tag — v3 of this patch specifically corrects this tag formatting, which is a reasonable thing to fix.
**Reviewed-by worthy:** Yes, this is a clean, correct documentation fix. No concerns.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-04 23:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 17:59 [PATCH v3] drm/gpusvm: Drop redundant @flags.* kernel-doc on struct drm_gpusvm_pages Shuicheng Lin
2026-05-01 22:39 ` Matthew Brost
2026-05-04 23:11 ` Claude Code Review Bot [this message]
2026-05-04 23:11 ` Claude review: " Claude Code Review Bot
-- strict thread matches above, loose matches on Subject: below --
2026-05-01 17:44 [PATCH v2] " Shuicheng Lin
2026-05-04 23:12 ` Claude review: " Claude Code Review Bot
2026-05-04 23:12 ` Claude Code Review Bot
2026-05-01 17:13 [PATCH] " Shuicheng Lin
2026-05-04 23:13 ` Claude review: " Claude Code Review Bot
2026-05-04 23:13 ` 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-20260501175956.4054088-1-shuicheng.lin@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