From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/tegra: tegra_drm.h: fix all uapi kernel-doc warnings
Date: Fri, 27 Feb 2026 11:38:40 +1000 [thread overview]
Message-ID: <review-overall-20260226215833.989397-1-rdunlap@infradead.org> (raw)
In-Reply-To: <20260226215833.989397-1-rdunlap@infradead.org>
Overall Series Review
Subject: drm/tegra: tegra_drm.h: fix all uapi kernel-doc warnings
Author: Randy Dunlap <rdunlap@infradead.org>
Patches: 1
Reviewed: 2026-02-27T11:38:40.851349
---
This is a single-patch series from Randy Dunlap that fixes kernel-doc warnings in the Tegra DRM UAPI header. The patch is straightforward and correct — it addresses two categories of warnings:
1. Missing `@cmdbuf` and `@target` member descriptions in `struct drm_tegra_reloc`.
2. Comments on `#define` macros incorrectly using `/**` (kernel-doc) style instead of plain `/*` comments.
The patch is clean, minimal, and does exactly what the commit message describes. No functional changes, no UAPI ABI changes, no risk of breakage.
**Recommendation: Accept.** This is a routine documentation cleanup patch.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-02-27 1:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 21:58 [PATCH] drm/tegra: tegra_drm.h: fix all uapi kernel-doc warnings Randy Dunlap
2026-02-27 1:38 ` Claude Code Review Bot [this message]
2026-02-27 1:38 ` Claude review: " Claude Code Review Bot
-- strict thread matches above, loose matches on Subject: below --
2026-03-04 1:41 [PATCH v2] " Randy Dunlap
2026-03-05 3:56 ` Claude review: " Claude Code Review Bot
2026-03-05 3:56 ` 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-20260226215833.989397-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