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:12:49 +1000 [thread overview]
Message-ID: <review-overall-20260501174435.4053381-1-shuicheng.lin@intel.com> (raw)
In-Reply-To: <20260501174435.4053381-1-shuicheng.lin@intel.com>
Overall Series Review
Subject: drm/gpusvm: Drop redundant @flags.* kernel-doc on struct drm_gpusvm_pages
Author: Shuicheng Lin <shuicheng.lin@intel.com>
Patches: 1
Reviewed: 2026-05-05T09:12:49.244063
---
This is a single trivial kernel-doc fix for `struct drm_gpusvm_pages` in `include/drm/drm_gpusvm.h`. The change is correct and well-motivated. The existing kernel-doc uses `@flags.*` dotted notation (e.g., `@flags.migrate_devmem`) to document sub-fields of the `flags` member, but that notation only works for **anonymous** embedded structs that kernel-doc flattens into the parent. Here, `flags` is of the named type `struct drm_gpusvm_pages_flags`, which already has its own kernel-doc block — so the dotted entries are redundant, don't match any flattened member, and generate "Excess struct member" warnings from `scripts/kernel-doc`.
The fix correctly drops the five `@flags.*` lines and replaces them with a single `@flags` entry using the `&struct drm_gpusvm_pages_flags` cross-reference. No functional change.
The commit message is clear and thorough, including the exact warnings being fixed and a link to the failing CI series. No concerns with the patch itself.
**Minor process note:** The patch lists `Assisted-by: GitHub Copilot` and Cc's `copilot@github.com`. While this is a trivial doc change, some subsystem maintainers have policies about AI-attribution tags — worth checking if drm-misc has any stance on this. The `Assisted-by:` tag is not an officially recognized kernel tag (unlike `Co-developed-by:` or `Suggested-by:`).
**Verdict:** Looks good. Trivial and correct fix.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-04 23:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 17:44 [PATCH v2] drm/gpusvm: Drop redundant @flags.* kernel-doc on struct drm_gpusvm_pages Shuicheng Lin
2026-05-04 23:12 ` Claude Code Review Bot [this message]
2026-05-04 23:12 ` Claude review: " Claude Code Review Bot
-- strict thread matches above, loose matches on Subject: below --
2026-05-01 17:59 [PATCH v3] " Shuicheng Lin
2026-05-04 23:11 ` Claude review: " Claude Code Review Bot
2026-05-04 23:11 ` 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-overall-20260501174435.4053381-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