From: Cyril Hrubis <chrubis@suse.cz>
To: Richard Palethorpe <rpalethorpe@suse.de>
Cc: Jan Kara <jack@suse.cz>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 2/3] fanotify10: Add support for multiple event files
Date: Tue, 22 Nov 2022 13:56:23 +0100 [thread overview]
Message-ID: <Y3zG93Qf28sxqqND@yuki> (raw)
In-Reply-To: <871qpvfa3c.fsf@suse.de>
Hi!
> > This is minor, but I would have named the macro FOREACH_PATH() and
> > added
>
> This is actually not in line with the kernel style. At least IIRC
> foreach macros are lower case in the instances I have seen. This is also
> what we have in tst_cgroup.c for e.g.
>
> > curly braces around the block. And the same for the rest of the
> > invocations.
>
> At some point checkpatch stopped complaining about this, so it's now the
> authors discretion whether to use curly braces in these cases. Unless
> there is something wrong with our checkpatch.
I do not think that this was ever enforced by checkpatch.
> IMO there is no mistaking that it is a loop macro with one function call
> in the body.
I tend to put the curly braces everywhere where there is a multiline
macro/function call because I find that way easier on the eyes...
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-11-22 12:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 12:47 [LTP] [PATCH 0/3] Make fanotify10 test yet more reliable Jan Kara
2022-11-15 12:47 ` [LTP] [PATCH 1/3] fanotify10: Use named initializers Jan Kara
2022-11-15 12:47 ` [LTP] [PATCH 2/3] fanotify10: Add support for multiple event files Jan Kara
2022-11-17 15:58 ` Petr Vorel
2022-11-21 9:14 ` Jan Kara
2022-11-21 9:33 ` Petr Vorel
2022-11-21 9:39 ` Cyril Hrubis
2022-11-22 8:19 ` Petr Vorel
2022-11-22 10:10 ` Petr Vorel
2022-11-21 9:53 ` Jan Kara
2022-11-21 14:24 ` Richard Palethorpe
2022-11-22 8:17 ` Petr Vorel
2022-11-22 8:57 ` Richard Palethorpe
2022-11-21 15:04 ` Cyril Hrubis
2022-11-22 12:10 ` Richard Palethorpe
2022-11-22 12:56 ` Cyril Hrubis [this message]
2022-11-15 12:47 ` [LTP] [PATCH 3/3] fanotify10: Make evictable marks tests more reliable Jan Kara
2022-11-16 2:17 ` Pengfei Xu
2022-11-16 10:58 ` Jan Kara
2022-11-16 16:32 ` Amir Goldstein
2022-11-17 15:50 ` Petr Vorel
2022-11-21 15:09 ` Cyril Hrubis
2022-11-22 10:30 ` Petr Vorel
2022-11-22 12:42 ` Cyril Hrubis
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=Y3zG93Qf28sxqqND@yuki \
--to=chrubis@suse.cz \
--cc=jack@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.de \
/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