From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm: fix some kernel-doc warnings
Date: Fri, 27 Feb 2026 12:40:46 +1000 [thread overview]
Message-ID: <review-overall-20260226030038.1182961-1-yujie.liu@intel.com> (raw)
In-Reply-To: <20260226030038.1182961-1-yujie.liu@intel.com>
Overall Series Review
Subject: drm: fix some kernel-doc warnings
Author: Yujie Liu <yujie.liu@intel.com>
Patches: 16
Reviewed: 2026-02-27T12:40:46.546401
---
This is a straightforward 7-patch series by Yujie Liu fixing kernel-doc warnings across various DRM subsystems. Each patch corrects a mismatch between the kernel-doc comment and the actual function prototype or parameter list. The fixes fall into three categories:
1. **Function name mismatches** (patches 1, 4, 5, 6, 7): The doc comment names a function that doesn't match the actual function definition, typically due to a rename that didn't update the comment.
2. **Missing parameter descriptions** (patches 2, 3): A parameter was added to a function but never documented.
3. **Parameter name mismatches** (patches 1, 7): The `@param` name in the doc doesn't match the actual parameter name.
All patches are trivially correct, include appropriate `Fixes:` tags pointing to the commits that introduced the mismatches, and are properly scoped (one logical fix per patch, with patch 3 bundling two related fixes in the same file). No functional code changes, zero risk of regressions.
**Verdict: Series looks good. All patches are correct and ready to apply.**
---
---
Generated by Claude Code Patch Reviewer
prev parent reply other threads:[~2026-02-27 2:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 3:00 [PATCH 0/7] drm: fix some kernel-doc warnings Yujie Liu
2026-02-26 3:00 ` [PATCH 1/7] drm/gpusvm: fix kernel-doc warning for drm_gpusvm_pages_valid_unlocked() Yujie Liu
2026-02-26 3:06 ` Matthew Brost
2026-02-26 5:56 ` Yujie Liu
2026-02-26 11:39 ` Christian König
2026-02-27 2:08 ` Yujie Liu
2026-02-27 2:40 ` Claude review: " Claude Code Review Bot
2026-02-26 3:00 ` [PATCH 2/7] drm/scheduler: fix kernel-doc warning for drm_sched_job_done() Yujie Liu
2026-02-27 2:40 ` Claude review: " Claude Code Review Bot
2026-02-26 3:00 ` [PATCH 3/7] drm/gma500: fix kernel-doc warning for framebuffer init/create functions Yujie Liu
2026-02-27 2:40 ` Claude review: " Claude Code Review Bot
2026-02-26 3:00 ` [PATCH 4/7] drm/amdgpu: fix kernel-doc warning for amdgpu_ttm_alloc_mmio_remap_bo() Yujie Liu
2026-02-26 16:52 ` Alex Deucher
2026-02-27 2:40 ` Claude review: " Claude Code Review Bot
2026-02-26 3:00 ` [PATCH 5/7] drm/xe/pf: fix kernel-doc warning for SR-IOV VF restore function Yujie Liu
2026-02-26 11:36 ` Michal Wajdeczko
2026-02-27 2:40 ` Claude review: " Claude Code Review Bot
2026-02-26 3:00 ` [PATCH 6/7] drm/amd/pm: fix kernel-doc warning for smu_msg_v1_send_msg() Yujie Liu
2026-02-26 16:54 ` Alex Deucher
2026-02-27 2:40 ` Claude review: " Claude Code Review Bot
2026-02-26 3:00 ` [PATCH 7/7] drm/amd/ras: fix kernel-doc warning for ras_eeprom_append() Yujie Liu
2026-02-26 16:53 ` Alex Deucher
2026-02-27 2:40 ` Claude review: " Claude Code Review Bot
2026-02-27 2:40 ` 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-overall-20260226030038.1182961-1-yujie.liu@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