From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/vmwgfx: fix kernel-doc warnings in vmwgfx_drv.h
Date: Mon, 23 Feb 2026 06:18:01 +1000 [thread overview]
Message-ID: <review-patch1-20260219215548.470810-1-rdunlap@infradead.org> (raw)
In-Reply-To: <20260219215548.470810-1-rdunlap@infradead.org>
Patch Review
The forward declarations were moved from between the kernel-doc comment and the struct definition to above the comment, which is the correct fix. However, the duplicate `struct vmw_bo;` was preserved:
> +struct vmw_bo;
> +struct vmw_bo;
> +struct vmw_resource_dirty;
The original code already had `struct vmw_bo;` twice. Moving them is the right thing to do, but this would have been a good opportunity to drop the duplicate. A duplicate forward declaration is harmless, but it looks like an oversight.
The `vmw_piter_page` return value description was updated to use the `Returns:` tag format, but the text itself is still wrong:
> +/**
> * vmw_piter_page - Return a pointer to the current page.
> *
> * @viter: Pointer to the iterator
> *
> + * Returns: the DMA address of the page pointed to by @viter.
The function returns a `struct page *`, not a DMA address. The brief description ("Return a pointer to the current page") is correct, but the `Returns:` line was copied from `vmw_piter_dma_addr` above it and was never fixed. Since this patch is specifically about making kernel-doc accurate, it would be worth correcting this to something like "Returns: pointer to the current page."
Everything else in the patch looks correct:
- The `struct vmw-resource` typo fix to `struct vmw_resource` is right.
- The `@mob_node;` to `@mob_node:` semicolon-to-colon fix is right.
- The `@num_regions` to `@num_pages` rename matches the actual struct member name (`unsigned long num_pages`).
- The `@memcpy` to `@do_cpy` rename matches the actual struct member (`void (*do_cpy)(...)`).
- The `@addr` to `@fifo_reg` rename matches the actual parameter name.
- The `/* private: */` markers for `vmw_res_cache_entry.private` and `vmw_dma_map_max` are appropriate.
- All the `/**` to `/*` conversions for section-heading comments are correct — these are not kernel-doc comments and should not use the `/**` prefix.
- The added `@filp`, `@used_prio`, `@dirty`, `@mode`, `@pages`, `@addrs`, `@fmt`, `@vmw`, `@value` descriptions all match actual struct members or function parameters.
---
Generated by Claude Code Patch Reviewer
prev parent reply other threads:[~2026-02-22 20:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 21:55 [PATCH RESEND] drm/vmwgfx: fix kernel-doc warnings in vmwgfx_drv.h Randy Dunlap
2026-02-22 20:18 ` Claude review: " Claude Code Review Bot
2026-02-22 20:18 ` 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-patch1-20260219215548.470810-1-rdunlap@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