From: sashiko-bot@kernel.org
To: UgwuRhema <hikarialiyev@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] staging: fbtft: fbtft-bus: remove space before close parenthesis
Date: Mon, 21 Sep 2026 18:18:31 +0000 [thread overview]
Message-ID: <20260921181831.DDAF41F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260921181350.89925-1-hikarialiyev@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] staging/fbtft: build failure due to missing macro argument
--
commit b334de9ec8bff5176150c0abed3949be6aea7f81
Author: UgwuRhema <hikarialiyev@gmail.com>
staging: fbtft: fbtft-bus: remove space before close parenthesis
This commit removes spaces before closing parentheses in fbtft-bus.c to fix
warnings from checkpatch.pl.
> 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)
[Severity: Low]
Does this cause a build failure? The macro define_fbtft_write_reg is
defined to take exactly 4 parameters:
#define define_fbtft_write_reg(func, buffer_type, data_type, modifier)
Removing the trailing comma means the macro is now invoked with only 3
arguments, which violates C preprocessor rules and results in a fatal
compiler error.
> 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 this also cause a preprocessor error for the same reason? The 4th
argument is missing here as well.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260921181350.89925-1-hikarialiyev@gmail.com?part=1
prev parent reply other threads:[~2026-09-21 18:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 18:13 [PATCH] staging: fbtft: fbtft-bus: remove space before close parenthesis UgwuRhema
2026-09-21 18:18 ` sashiko-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=20260921181831.DDAF41F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hikarialiyev@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
/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.