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:00 +1000 [thread overview]
Message-ID: <review-overall-20260219215548.470810-1-rdunlap@infradead.org> (raw)
In-Reply-To: <20260219215548.470810-1-rdunlap@infradead.org>
Overall Series Review
Subject: drm/vmwgfx: fix kernel-doc warnings in vmwgfx_drv.h
Author: Randy Dunlap <rdunlap@infradead.org>
Patches: 1
Reviewed: 2026-02-23T06:18:00.845881
---
This is a single-patch series from Randy Dunlap that fixes 45+ kernel-doc warnings in `vmwgfx_drv.h`. The changes are purely documentation: fixing struct/member comment formatting, adding missing parameter and return value descriptions, correcting a struct name typo (`vmw-resource` to `vmw_resource`), converting non-kernel-doc section-header comments from `/**` to `/*`, and marking private members/enum values with `private:`.
The patch is straightforward documentation cleanup with no functional code changes. It does contain two minor issues worth noting: a duplicate forward declaration that was carried forward, and a pre-existing documentation error in a return value description that the patch perpetuates rather than fixing.
---
Generated by Claude Code Patch Reviewer
next 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 Code Review Bot [this message]
2026-02-22 20:18 ` Claude review: " 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-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