From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/gpusvm: correct kernel-doc for drm_gpusvm_pages_valid_unlocked()
Date: Mon, 23 Feb 2026 06:21:10 +1000 [thread overview]
Message-ID: <review-overall-20260219215510.466906-1-rdunlap@infradead.org> (raw)
In-Reply-To: <20260219215510.466906-1-rdunlap@infradead.org>
Overall Series Review
Subject: drm/gpusvm: correct kernel-doc for drm_gpusvm_pages_valid_unlocked()
Author: Randy Dunlap <rdunlap@infradead.org>
Patches: 1
Reviewed: 2026-02-23T06:21:10.333996
---
This is a single-patch series that fixes kernel-doc warnings for the `drm_gpusvm_pages_valid_unlocked()` function in `drivers/gpu/drm/drm_gpusvm.c`. The function was apparently renamed from `drm_gpusvm_range_pages_valid_unlocked()` at some point (likely when refactoring to use `struct drm_gpusvm_pages` instead of `struct drm_gpusvm_range`), but the kernel-doc comment block was not updated to reflect the new function name and parameter. This patch corrects both the function name and the parameter description in the doc comment.
The fix is trivially correct and resolves two concrete `kernel-doc` warnings cited in the commit message.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-02-22 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 21:55 [PATCH v2] drm/gpusvm: correct kernel-doc for drm_gpusvm_pages_valid_unlocked() Randy Dunlap
2026-02-22 20:21 ` Claude Code Review Bot [this message]
2026-02-22 20:21 ` 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-20260219215510.466906-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