Linux-Fsdevel Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: Joe Perches <joe@perches.com>
Cc: Jiri Kosina <trivial@kernel.org>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 23/29] fuse: Avoid comma separated statements
Date: Mon, 1 Feb 2021 09:12:25 +0100	[thread overview]
Message-ID: <CAJfpegtp9zC5u+D=YJt3Ec-moALCJxkVswmZEFJWb-VXfLXmaA@mail.gmail.com> (raw)
In-Reply-To: <1ccd477e845fe5a114960c6088612945e1a22f23.1598331149.git.joe@perches.com>

On Tue, Aug 25, 2020 at 6:57 AM Joe Perches <joe@perches.com> wrote:
>
> Use semicolons and braces.

Reference to coding style doc?  Or other important reason?  Or just
personal preference?

Thanks,
Miklos

  parent reply	other threads:[~2021-02-01  8:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-25  4:55 [PATCH 00/29] treewide: Convert " Joe Perches
2020-08-25  4:56 ` [PATCH 23/29] fuse: Avoid " Joe Perches
2021-01-30 19:04   ` Joe Perches
2021-02-01  8:12   ` Miklos Szeredi [this message]
2020-09-09  2:09 ` [PATCH 00/29] treewide: Convert " Martin K. Petersen

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='CAJfpegtp9zC5u+D=YJt3Ec-moALCJxkVswmZEFJWb-VXfLXmaA@mail.gmail.com' \
    --to=miklos@szeredi.hu \
    --cc=joe@perches.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@kernel.org \
    --subject='Re: [PATCH 23/29] fuse: Avoid comma separated statements' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).