From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Julia Lawall <Julia.Lawall@inria.fr>
Cc: "Hauke Mehrtens" <hauke@hauke-m.de>,
kernel-janitors@vger.kernel.org,
"Rafał Miłecki" <zajec5@gmail.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: BCM47XX: drop unneeded semicolon
Date: Mon, 3 Aug 2026 15:10:56 +0200 [thread overview]
Message-ID: <anCTYCQoovqgSjLH@alpha.franken.de> (raw)
In-Reply-To: <20260801191002.1383835-16-Julia.Lawall@inria.fr>
On Sat, Aug 01, 2026 at 09:10:02PM +0200, Julia Lawall wrote:
> When a function-like macro expands to an expression, that expression
> doesn't need a semicolon after it. All uses have been verified to
> have their own semicolons.
>
> This was found using the following Coccinelle semantic patch:
>
> @r@
> identifier i : script:ocaml() { String.lowercase_ascii i = i };
> expression e;
> @@
>
> *#define i(...) e;
>
> Signed-off-by: Julia Lawall <Julia.Lawall@inria.fr>
>
> ---
> arch/mips/bcm47xx/buttons.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/mips/bcm47xx/buttons.c b/arch/mips/bcm47xx/buttons.c
> index 46994f9bb..e76ca34c8 100644
> --- a/arch/mips/bcm47xx/buttons.c
> +++ b/arch/mips/bcm47xx/buttons.c
> @@ -512,7 +512,7 @@ static int __init bcm47xx_buttons_copy(const struct gpio_keys_button *buttons,
> }
>
> #define bcm47xx_copy_bdata(dev_buttons) \
> - bcm47xx_buttons_copy(dev_buttons, ARRAY_SIZE(dev_buttons));
> + bcm47xx_buttons_copy(dev_buttons, ARRAY_SIZE(dev_buttons))
not applicable to mips-next, because commit 27c61f8565a4 ("MIPS: BCM47XX:
Convert buttons to software nodes") removed it.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2026-08-03 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 19:10 [PATCH] MIPS: BCM47XX: drop unneeded semicolon Julia Lawall
2026-08-02 15:17 ` Philippe Mathieu-Daudé
2026-08-03 13:10 ` Thomas Bogendoerfer [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=anCTYCQoovqgSjLH@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=Julia.Lawall@inria.fr \
--cc=hauke@hauke-m.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=zajec5@gmail.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