From: Cyril Hrubis <chrubis@suse.cz>
To: Jinseok Kim <always.starving0@gmail.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [RFC] testcases: unify naming for syscall tests ending in digits
Date: Mon, 4 May 2026 10:31:22 +0200 [thread overview]
Message-ID: <afhZWvFkvOBd5w7Q@yuki.lan> (raw)
In-Reply-To: <20260430150942.4859-1-always.starving0@gmail.com>
Hi!
> I noticed both styles are used for tests of syscalls ending in digits:
>
> For example:
> dup2/dup201.c
> dup3/dup3_01.c
>
> Would it be better to unify them as dup2_01.c / dup3_01.c for consistency?
It makes sense to unify, I'm not sure if it should be dup201.c and
dup301.c or dup2_01.c and dup3_02.c.
If we want to keep the naming consistent with the rest of LTP we should
probably go for dup201.c and dup301.c but it's a bit less readable than
the underscore variant.
Does anyone else has an opinion here?
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-05-04 8:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 15:09 [LTP] [RFC] testcases: unify naming for syscall tests ending in digits Jinseok Kim
2026-05-04 8:31 ` Cyril Hrubis [this message]
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=afhZWvFkvOBd5w7Q@yuki.lan \
--to=chrubis@suse.cz \
--cc=always.starving0@gmail.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