From: sashiko-bot@kernel.org
To: wrmfwv@163.com
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] staging: fbtft: fix syntax errors in macros
Date: Sun, 18 Oct 2026 08:58:43 +0000 [thread overview]
Message-ID: <sashiko-outbox-176013@kernel.org> (raw)
In-Reply-To: <20261018085345.17619-1-wrmfwv@163.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] staging: fbtft: missing argument in define_fbtft_write_reg() breaks build
--
commit b28f14a98f84b888195dbf0a2f659dbf742f021c
Author: gtl-m <admin@micronull.cn>
staging: fbtft: fix syntax errors in macros
This commit removes trailing commas and spaces before closing parentheses in
two define_fbtft_write_reg() macro invocations to address checkpatch.pl
warnings.
> diff --git a/drivers/staging/fbtft/fbtft-bus.c b/drivers/staging/fbtft/fbtft-bus.c
> index 30e436ff19e4c..409770891c548 100644
> --- a/drivers/staging/fbtft/fbtft-bus.c
> +++ b/drivers/staging/fbtft/fbtft-bus.c
> @@ -62,9 +62,9 @@ out: \
> } \
> EXPORT_SYMBOL(func);
>
> -define_fbtft_write_reg(fbtft_write_reg8_bus8, u8, u8, )
> +define_fbtft_write_reg(fbtft_write_reg8_bus8, u8, u8)
> define_fbtft_write_reg(fbtft_write_reg16_bus8, __be16, u16, cpu_to_be16)
> -define_fbtft_write_reg(fbtft_write_reg16_bus16, u16, u16, )
> +define_fbtft_write_reg(fbtft_write_reg16_bus16, u16, u16)
[Severity: Low]
Does removing the trailing comma break the build when CONFIG_FB_TFT is
enabled?
In drivers/staging/fbtft/fbtft-bus.c, define_fbtft_write_reg() is defined
as a 4-argument macro:
#define define_fbtft_write_reg(func, buffer_type, data_type, modifier) \
void func(struct fbtft_par *par, int len, ...) \
{ \
...
*buf = modifier((data_type)va_arg(args, unsigned int)); \
For fbtft_write_reg8_bus8() and fbtft_write_reg16_bus16(), no byte-order
conversion modifier is needed, so the trailing comma intentionally passes an
empty fourth argument to the macro. Removing the comma passes only 3
arguments to a 4-parameter macro, causing the C preprocessor to fail the
build.
>
> void fbtft_write_reg8_bus9(struct fbtft_par *par, int len, ...)
> {
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261018085345.17619-1-wrmfwv@163.com?part=1
next prev parent reply other threads:[~2026-10-18 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 8:53 [PATCH] staging: fbtft: fix syntax errors in macros wrmfwv
2026-10-18 8:58 ` sashiko-bot [this message]
2026-10-18 9:54 ` Greg KH
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=sashiko-outbox-176013@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wrmfwv@163.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.