From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] checkpatch: relax parenthesis style checks
Date: Fri, 24 Jul 2026 13:31:19 +0200 [thread overview]
Message-ID: <20260724113119.GA876268@pevik> (raw)
In-Reply-To: <6a60b4f2.332cc45f.161033.23b2@mx.google.com>
> > I'd say it depends how your displays tabs (if tabs are in the sources, we have
> > .editorconfig, but not all not all developers have their editor set to use it).
> > In certain setup it does not look OK + the problem of inconsistency, but I'm ok
> > to ignore it.
> At the moment i use the standard kernel guidelines for TAB (8 spaces)
> > > > * OPEN_ENDED_LINE asks for not ending line with '(' or '['.
> > > > i.e. instead of this:
> > > > ruleset_fd = TST_EXP_FD_SILENT(
> > > > tst_syscall(__NR_landlock_create_ruleset, ruleset_attr,
> > > > sizeof(struct tst_landlock_ruleset_attr_abi1), 0));
> > > > have this:
> > > > ruleset_fd = TST_EXP_FD_SILENT(tst_syscall(__NR_landlock_create_ruleset, ruleset_attr,
> > > > sizeof(struct tst_landlock_ruleset_attr_abi1), 0));
> > > you choose the right example, landlock testing suite has been updated to
> > > match this rule and now it has stuff like:
> > > apply_landlock_fs_layer(ruleset_attr, sizeof(struct tst_landlock_ruleset_attr_abi1),
> > > path_beneath_attr, MNTPOINT, LANDLOCK_ACCESS_FS_IOCTL_DEV);
> For some reason my email client is not showing the correct spaces in the
> example:
> my_ret_val = apply_landlock_fs_layer(ruleset_attr, sizeof(struct tst_landlock_ruleset_attr_abi1),
> path_beneath_attr, MNTPOINT, LANDLOCK_ACCESS_FS_IOCTL_DEV);
> or:
> my_ret_val = apply_landlock_fs_layer(ruleset_attr,
> sizeof(struct tst_landlock_ruleset_attr_abi1),
> path_beneath_attr,
> MNTPOINT, LANDLOCK_ACCESS_FS_IOCTL_DEV);
> to escape the 80-100 lines rule.
As I wrote, I prefer more arguments in the line than a single one.
Anyway, I tend to send RFC patch to add OPEN_ENDED_LINE, to see what others
think about it. But if you're strongly against it, I would not want to enforce
you.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-07-24 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 8:32 [LTP] [PATCH] checkpatch: relax parenthesis style checks Andrea Cervesato
2026-07-14 8:50 ` Cyril Hrubis
2026-07-22 6:32 ` Petr Vorel
2026-07-22 7:26 ` Andrea Cervesato via ltp
2026-07-22 8:04 ` Petr Vorel
2026-07-22 12:17 ` Andrea Cervesato via ltp
2026-07-24 11:31 ` Petr Vorel [this message]
2026-07-14 10:47 ` [LTP] " linuxtestproject.agent
2026-07-21 15:22 ` [LTP] [PATCH] " Andrea Cervesato via ltp
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=20260724113119.GA876268@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.com \
--cc=ltp@lists.linux.it \
/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