From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: Re: [PATCH] staging: fbtft: replace sprintf with snprintf
Date: Thu, 04 Jun 2026 14:40:17 +1000 [thread overview]
Message-ID: <review-overall-2026060110-unlisted-headache-aec7@gregkh> (raw)
In-Reply-To: <2026060110-unlisted-headache-aec7@gregkh>
Overall Series Review
Subject: Re: [PATCH] staging: fbtft: replace sprintf with snprintf
Author: Greg KH <gregkh@linuxfoundation.org>
Patches: 8
Reviewed: 2026-06-04T14:40:17.699184
---
This is a single-patch submission that replaces `sprintf` with `snprintf` in `fbtft_register_framebuffer()` in the staging fbtft driver. The change is functionally correct but has several submission quality issues that would likely result in the patch being rejected in its current form.
**Submission issues:**
1. The patch was sent as a **base64-encoded MIME attachment** rather than inline in the email body. Kernel patches must be sent inline per `Documentation/process/submitting-patches.rst`. Tools like `git send-email` should be used.
2. The **commit message has no body** — the Signed-off-by immediately follows the subject. The cover letter text ("This patch replaces unsafe sprintf calls...") should be the commit message body, not just in the email.
3. The **From name** in the email ("Enchanted Hunter") doesn't match the **Signed-off-by name** ("rat1bor"). The kernel requires a real name for contributions; pseudonyms are generally not accepted.
4. The commit message in the cover letter body has formatting errors: "infbtft_register_framebuffer()" (missing space after "in") and "overflow.Signed-off-by" (missing newline before the tag).
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-06-04 4:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 0:43 [PATCH] staging: fbtft: replace sprintf with snprintf Enchanted Hunter
2026-06-01 5:44 ` Greg KH
2026-06-04 4:40 ` Claude Code Review Bot [this message]
2026-06-04 4:40 ` Claude review: " Claude Code Review Bot
2026-06-01 8:25 ` Andy Shevchenko
2026-06-02 17:12 ` Enchanted Hunter
2026-06-02 18:31 ` Andy Shevchenko
2026-06-02 19:33 ` Enchanted Hunter
2026-06-03 1:13 ` Andy Shevchenko
2026-06-03 9:14 ` Enchanted Hunter
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-2026060110-unlisted-headache-aec7@gregkh \
--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