From: Jinseok Kim <always.starving0@gmail.com>
To: ltp@lists.linux.it
Subject: [LTP] [RFC] testcases: unify naming for syscall tests ending in digits
Date: Fri, 1 May 2026 00:09:09 +0900 [thread overview]
Message-ID: <20260430150942.4859-1-always.starving0@gmail.com> (raw)
Hi All,
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?
Thanks.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2026-04-30 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 15:09 Jinseok Kim [this message]
2026-05-04 8:31 ` [LTP] [RFC] testcases: unify naming for syscall tests ending in digits 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=20260430150942.4859-1-always.starving0@gmail.com \
--to=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