From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: Re: [PATCH] accel/amdxdna: fix missing newline in pr_err message
Date: Sun, 22 Mar 2026 03:46:13 +1000 [thread overview]
Message-ID: <review-patch1-1af543d3-46ff-7a9c-6432-fe3c9050e23d@amd.com> (raw)
In-Reply-To: <1af543d3-46ff-7a9c-6432-fe3c9050e23d@amd.com>
Patch Review
**Verdict: Correct, minor nits only.**
The change itself is straightforward and correct:
```c
- pr_err("Ring buf size must be power of 2");
+ pr_err("Ring buf size must be power of 2\n");
```
I confirmed the current drm-next tree still has the missing newline at `drivers/accel/amdxdna/amdxdna_mailbox.c:502`, so this fix is still needed.
**Nits:**
1. **Signed-off-by name**: The `Signed-off-by: haoyu.lu <hechushiguitu666@gmail.com>` should use the author's real name, e.g., `Signed-off-by: Haoyu Lu <hechushiguitu666@gmail.com>`, consistent with the `From:` header and kernel conventions (see `Documentation/process/submitting-patches.rst`).
2. **Consider dev_err()**: This `pr_err()` could potentially be converted to `dev_err()` to include device context in the log message, making it easier to identify which device triggered the error in multi-device systems. However, that would be a separate cleanup patch and is outside the scope of this fix.
3. **Commit message**: The commit message is adequate but could mention the specific consequence (log line concatenation with subsequent messages) to explain *why* the newline matters.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-03-21 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 11:29 [PATCH] accel/amdxdna: fix missing newline in pr_err message Haoyu Lu
2026-03-20 15:54 ` Lizhi Hou
2026-03-21 17:46 ` Claude review: " Claude Code Review Bot
2026-03-21 17:46 ` Claude Code Review Bot [this message]
2026-03-23 3:49 ` [PATCH v2] " Haoyu Lu
2026-03-23 16:40 ` Lizhi Hou
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-patch1-1af543d3-46ff-7a9c-6432-fe3c9050e23d@amd.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