From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 3/3] shell API: Rename LTP_IPC_PATH -> TST_IPC_PATH
Date: Wed, 25 Aug 2021 11:04:57 +0200 [thread overview]
Message-ID: <YSYHuczVmaLlVG3D@pevik> (raw)
In-Reply-To: <8d74045f-3ebc-526d-f875-6ca121475a4d@jv-coder.de>
Hi Joerg,
> > Keep the old name in the legacy API.
> That doesn't make sense. If you update the variable name in the c api, you
> also have to update the old shell api (i.e. test.sh).
Ah, shell API implementation obviously depends on C API. Thanks for info.
> Or maybe even remove the code from the old shell api completely. As far as I
> see there are no users of the checkpoint api anymore.
> Both tests (cn_pec and memcfg/functional) were rewritten. It is probably
> safe to just drop the old api?
I'll check it, if it's really not used in the legacy API, I'd be also for removing it.
Kind regards,
Petr
next prev parent reply other threads:[~2021-08-25 9:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 8:09 [LTP] [PATCH 0/3] New API: Rename LTP_IPC_PATH -> TST_IPC_PATH Petr Vorel
2021-08-25 8:09 ` [LTP] [PATCH 1/3] lib: Move IPC_ENV_VAR definition into header Petr Vorel
2021-08-25 9:21 ` Cyril Hrubis
2021-08-25 10:21 ` Petr Vorel
2021-08-25 8:09 ` [LTP] [PATCH 2/3] C API: Rename LTP_IPC_PATH -> TST_IPC_PATH Petr Vorel
2021-08-25 8:15 ` Joerg Vehlow
2021-08-25 9:00 ` Petr Vorel
2021-08-25 9:08 ` Joerg Vehlow
2021-08-25 8:09 ` [LTP] [PATCH 3/3] shell " Petr Vorel
2021-08-25 8:18 ` Joerg Vehlow
2021-08-25 9:04 ` Petr Vorel [this message]
2021-08-25 9:00 ` [LTP] [PATCH 0/3] New " Cyril Hrubis
2021-08-25 9:09 ` Petr Vorel
2021-08-25 9:20 ` Cyril Hrubis
2021-08-25 10:23 ` Petr Vorel
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=YSYHuczVmaLlVG3D@pevik \
--to=pvorel@suse.cz \
--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