From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: Re: [PATCH v3] staging: fbtft: replace empty macro args with identity converter
Date: Mon, 13 Apr 2026 18:50:47 +1000 [thread overview]
Message-ID: <review-patch1-CAHp75VcdWMvvM-oKTqRACSXSUiVsEh1Ep_82MsJxfbrG4thUdA@mail.gmail.com> (raw)
In-Reply-To: <CAHp75VcdWMvvM-oKTqRACSXSUiVsEh1Ep_82MsJxfbrG4thUdA@mail.gmail.com>
Patch Review
**Verdict: NAK — this patch is broken and must not be applied.**
The macro `define_fbtft_write_reg` is defined with 4 parameters:
```c
#define define_fbtft_write_reg(func, buffer_type, data_type, modifier)
```
And `modifier` is used as a function-like call in the body (line 25, 42, 55 of the source):
```c
buf[i] = modifier((data_type)va_arg(args, unsigned int));
```
The patch changes:
```c
-define_fbtft_write_reg(fbtft_write_reg8_bus8, u8, u8, )
+define_fbtft_write_reg(fbtft_write_reg8_bus8, u8, u8)
```
This passes **3 arguments** to a **4-parameter macro**, which is a preprocessor error in standard C (C99 §6.10.3). This would fail to compile. The trailing comma with an empty token was not just whitespace — it was the empty 4th argument, which expands to nothing and effectively makes `modifier(expr)` become just `(expr)`.
The commit message describes this as fixing a "coding style issue reported by checkpatch.pl," but the proposed fix introduces a build break.
---
---
Generated by Claude Code Patch Reviewer
prev parent reply other threads:[~2026-04-13 8:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-12 17:33 [PATCH] staging: fbtft: fix coding style issue in fbtft-bus.c Baker
2026-04-12 17:33 ` [PATCH v3] staging: fbtft: replace empty macro args with identity converter Baker
2026-04-13 5:58 ` Andy Shevchenko
2026-04-13 6:03 ` Greg KH
2026-04-13 6:08 ` Andy Shevchenko
2026-04-13 8:50 ` Claude review: " Claude Code Review Bot
2026-04-13 8:50 ` Claude Code Review Bot
2026-04-13 8:50 ` 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-patch1-CAHp75VcdWMvvM-oKTqRACSXSUiVsEh1Ep_82MsJxfbrG4thUdA@mail.gmail.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