From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/rcar-du: Drop superfluous spaces after assignments
Date: Tue, 05 May 2026 08:30:43 +1000 [thread overview]
Message-ID: <review-overall-80e30578b6dd86664112320616c460c48dbd79f6.1777881435.git.geert+renesas@glider.be> (raw)
In-Reply-To: <80e30578b6dd86664112320616c460c48dbd79f6.1777881435.git.geert+renesas@glider.be>
Overall Series Review
Subject: drm/rcar-du: Drop superfluous spaces after assignments
Author: Geert Uytterhoeven <geert+renesas@glider.be>
Patches: 2
Reviewed: 2026-05-05T08:30:43.887825
---
This is a single-patch cosmetic cleanup from Geert Uytterhoeven targeting `drivers/gpu/drm/renesas/rcar-du/rcar_du_drv.c`. It removes superfluous double spaces after `=` in struct initializer assignments (`.dpll_mask = BIT(...)` → `.dpll_mask = BIT(...)`). The patch is trivially correct and has no functional impact.
**Verdict: No issues. Patch looks good.**
The commit message is clear, the cover-letter note about the pattern being copied from two original instances across SoC additions is a nice touch of context. All 10 hunks are mechanically identical in nature — removing one extra space character.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-04 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 7:58 [PATCH] drm/rcar-du: Drop superfluous spaces after assignments Geert Uytterhoeven
2026-05-04 8:11 ` Kieran Bingham
2026-05-04 22:30 ` Claude Code Review Bot [this message]
2026-05-04 22:30 ` 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-80e30578b6dd86664112320616c460c48dbd79f6.1777881435.git.geert+renesas@glider.be \
--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