From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Li Wang" <liwang@redhat.com>, <ltp@lists.linux.it>
Cc: Pradeep Susarla <pradeep.susarla@gmail.com>
Subject: Re: [LTP] [PATCH] libs: adopt lib* prefix instead of tst_* for libs/
Date: Mon, 12 Jan 2026 13:59:01 +0100 [thread overview]
Message-ID: <DFMMND84JK0B.27NIM2SX4YYGR@suse.com> (raw)
In-Reply-To: <20260109023914.45555-1-liwang@redhat.com>
Hi!
I generally agree with this approach, but I have the feeling we are
mixing naming a bit here. For instance, we have headers like ipcmsg.h
that has no functions starting with tst_*, while tst_numa.h does. Also,
the tst_* prefix for files has the clear goal to state we are importing
some LTP functionalities inside the tests code.
Said so, I would rather rename all LTP libraries as tst_*.h and to
rename functions inside them with tst_* prefix. In this way, we know
at the very first look, when a library is imported from LTP and not
from other sources.
--
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-01-12 12:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 2:39 [LTP] [PATCH] libs: adopt lib* prefix instead of tst_* for libs/ Li Wang via ltp
2026-01-09 3:07 ` Li Wang via ltp
2026-01-12 12:59 ` Andrea Cervesato via ltp [this message]
2026-01-12 14:10 ` Li Wang via ltp
2026-01-13 11:51 ` Petr Vorel
2026-01-13 13:30 ` Jan Stancek via ltp
2026-01-13 13:41 ` Andrea Cervesato via ltp
2026-01-14 3:03 ` Li Wang via ltp
2026-01-14 8:51 ` Petr Vorel
2026-01-14 10:32 ` Li Wang via ltp
2026-01-14 11:33 ` Petr Vorel
2026-01-14 11:58 ` Li Wang via ltp
2026-01-14 12:18 ` Jan Stancek via ltp
2026-01-14 12:07 ` Andrea Cervesato via ltp
2026-01-14 12:47 ` Li Wang via ltp
2026-01-14 13:36 ` 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=DFMMND84JK0B.27NIM2SX4YYGR@suse.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=liwang@redhat.com \
--cc=pradeep.susarla@gmail.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.