All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Petr Vorel" <pvorel@suse.cz>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] checkpatch: relax parenthesis style checks
Date: Wed, 22 Jul 2026 12:17:53 +0000	[thread overview]
Message-ID: <6a60b4f2.332cc45f.161033.23b2@mx.google.com> (raw)
In-Reply-To: <20260722080456.GA826637@pevik>

> 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.

--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-07-22 12:18 UTC|newest]

Thread overview: 8+ 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 [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=6a60b4f2.332cc45f.161033.23b2@mx.google.com \
    --to=ltp@lists.linux.it \
    --cc=andrea.cervesato@suse.com \
    --cc=pvorel@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.