From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Jan Polensky" <japo@linux.ibm.com>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v2 1/1] editorconfig: add consistent formatting rules for LTP
Date: Fri, 27 Mar 2026 10:53:09 +0000 [thread overview]
Message-ID: <69c66196.5d0a0220.2a94f1.b1f7@mx.google.com> (raw)
In-Reply-To: <20260316130320.138328-1-japo@linux.ibm.com>
Hi Jan,
> # C/Assembly source files, headers, and shell files use tabs
> [{*.{c,h,S,sh},ver_linux}]
> indent_style = tab
> indent_size = 4
LTP follows Linux kernel coding style, which uses 8-character-wide tabs.
This should be indent_size = 8.
> # Python and Perl: default to tabs (most test files use tabs, checkpatch.pl which we modify)
> [*.{py,pl}]
> indent_style = tab
> indent_size = 8
Not 100% sure about this.
The Python test files in the tree (e.g. pm_sched_domain.py, pm_ilb_test.py)
all use 4-space indentation, not tabs. The default for *.py should be
indent_style = space / indent_size = 4. Perl (checkpatch.pl) does use tabs,
so it should get its own section.
Also kirk uses 4 tabs indentation. So I guess we need to invert the two rules
at this point.
Regards,
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-03-27 10:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 13:03 [LTP] [PATCH v2 1/1] editorconfig: add consistent formatting rules for LTP Jan Polensky
2026-03-27 10:53 ` Andrea Cervesato via ltp [this message]
2026-03-27 12:33 ` Petr Vorel
2026-03-27 13:39 ` Andrea Cervesato via ltp
2026-03-27 17:43 ` Petr Vorel
2026-03-27 18:25 ` Jan Polensky
2026-03-27 18:59 ` Petr Vorel
2026-03-27 15:29 ` Petr Vorel
2026-03-27 17:55 ` Jan Polensky
2026-03-27 18:25 ` Petr Vorel
2026-03-30 7:23 ` Andrea Cervesato via ltp
2026-03-31 19:59 ` Jan Polensky
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=69c66196.5d0a0220.2a94f1.b1f7@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=japo@linux.ibm.com \
/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.