From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Julia Lawall <Julia.Lawall@inria.fr>
Cc: Steven Rostedt <rostedt@goodmis.org>,
kernel-janitors@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] ring-buffer: drop unneeded semicolon
Date: Mon, 3 Aug 2026 14:12:43 +0900 [thread overview]
Message-ID: <20260803141243.26f277cde804b03f37f2f126@kernel.org> (raw)
In-Reply-To: <20260801191002.1383835-6-Julia.Lawall@inria.fr>
On Sat, 1 Aug 2026 21:09:52 +0200
Julia Lawall <Julia.Lawall@inria.fr> 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>
>
Looks good to me.
Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> ---
> kernel/trace/ring_buffer.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
> index 8e2485bb3..7749dd2ac 100644
> --- a/kernel/trace/ring_buffer.c
> +++ b/kernel/trace/ring_buffer.c
> @@ -405,11 +405,11 @@ static void free_buffer_page(struct buffer_page *bpage)
> */
> #define alloc_cpu_buffer(cpu) (struct ring_buffer_per_cpu *) \
> kzalloc_node(ALIGN(sizeof(struct ring_buffer_per_cpu), \
> - cache_line_size()), GFP_KERNEL, cpu_to_node(cpu));
> + cache_line_size()), GFP_KERNEL, cpu_to_node(cpu))
>
> #define alloc_cpu_page(cpu) (struct buffer_page *) \
> kzalloc_node(ALIGN(sizeof(struct buffer_page), \
> - cache_line_size()), GFP_KERNEL, cpu_to_node(cpu));
> + cache_line_size()), GFP_KERNEL, cpu_to_node(cpu))
>
> static struct buffer_data_page *alloc_cpu_data(int cpu, int order)
> {
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2026-08-03 5:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 19:09 [PATCH] ring-buffer: drop unneeded semicolon Julia Lawall
2026-08-03 5:12 ` Masami Hiramatsu [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=20260803141243.26f277cde804b03f37f2f126@kernel.org \
--to=mhiramat@kernel.org \
--cc=Julia.Lawall@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
/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