New API: Rename LTP_IPC_PATH -> TST_IPC_PATH
Get series with b4
b4 am YSYGy3cewt9Sseb/@yukiVersions newest first
- v1 Latest1 of 3 patches 0 repliesNew
1 of 3 patches is in this archive. The cover letter announces 3.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | lib: Move IPC_ENV_VAR definition into header | +0 | 1 reply |
Reviews trailers per patch
The patch has a Reviewed-by or Acked-by.
| Patch | Cyril Hrubis |
|---|---|
| 1/3 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [LTP] [PATCH 0/3] New API: Rename LTP_IPC_PATH -> TST_IPC_PATH
Hi!
Quoted 9 lines
Quoted 3 lines
As it is it's pretty clear where the environment variable comes from, if we rename it to
TST_IPC_PATHit's not obvious that this has been exported by LTP test.I was thinking about it as well (just forget to write that into cover letter).
Quoted 2 lines
Generally things that are visible on the running system tends to be prefixed with
LTP_orltp_rather thanTST_ortst_...Sure. I just thought that
LTP_is for variables which are expected to be set by user. But let's keep the old name. How about the first commit (cleanup)?
There is no such rule I guess.
It has been case by case, for instance we do have KCONFIG_PATH which we agreed on with the testing community to be a canonical variable name that is shared between different frameworks.
Signature · 2 lines
Cyril Hrubis [email protected]