From: Al Viro <viro@zeniv.linux.org.uk>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
NeilBrown <neil@brown.name>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] mqueue: remove duplicated ; at end of statement
Date: Fri, 19 Dec 2025 10:23:59 +0000 [thread overview]
Message-ID: <20251219102359.GY1712166@ZenIV> (raw)
In-Reply-To: <20251219101941.463509-1-colin.i.king@gmail.com>
On Fri, Dec 19, 2025 at 10:19:41AM +0000, Colin Ian King wrote:
> There is a duplicated semicolon at the end of a statement,
> remove it.
FWIW, that's dealt with in the series I've posted lately - see
viro/vfs.git #work.filename, if you prefer to look at it in
git. I'm going to put that into -next this weekend, assuming nobody
posts objections.
prev parent reply other threads:[~2025-12-19 10:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 10:19 [PATCH][next] mqueue: remove duplicated ; at end of statement Colin Ian King
2025-12-19 10:23 ` Al Viro [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=20251219102359.GY1712166@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=brauner@kernel.org \
--cc=colin.i.king@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil@brown.name \
/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