From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/gpusvm: Fix drm_gpusvm_pages_valid_unlocked() kernel-doc
Date: Mon, 23 Feb 2026 06:29:02 +1000 [thread overview]
Message-ID: <review-overall-20260219205029.1011336-1-matthew.brost@intel.com> (raw)
In-Reply-To: <20260219205029.1011336-1-matthew.brost@intel.com>
Overall Series Review
Subject: drm/gpusvm: Fix drm_gpusvm_pages_valid_unlocked() kernel-doc
Author: Matthew Brost <matthew.brost@intel.com>
Patches: 1
Reviewed: 2026-02-23T06:29:02.386965
---
This is a single-patch series that fixes stale kernel-doc comments for `drm_gpusvm_pages_valid_unlocked()`. The function was apparently renamed from `drm_gpusvm_range_pages_valid_unlocked()` and its second parameter changed from `range` (of type `struct drm_gpusvm_range *`) to `svm_pages` (of type `struct drm_gpusvm_pages *`), but the kernel-doc comment was not updated at that time. This patch corrects that oversight.
The fix is accurate: the kernel-doc function name, parameter name, and description now match the actual function signature and semantics. No functional code is changed.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-02-22 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 20:50 [PATCH] drm/gpusvm: Fix drm_gpusvm_pages_valid_unlocked() kernel-doc Matthew Brost
2026-02-22 20:29 ` Claude Code Review Bot [this message]
2026-02-22 20:29 ` 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-20260219205029.1011336-1-matthew.brost@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