Skip to content

New API: Rename LTP_IPC_PATH -> TST_IPC_PATH

Cyril Hrubis ltp 1 version New

Get series with b4
b4 am YSYGy3cewt9Sseb/@yuki

Versions newest first

  1. 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 filesSizeRepliesApplied
1/3lib: Move IPC_ENV_VAR definition into header+0 -01 reply

Reviews trailers per patch

The patch has a Reviewed-by or Acked-by.

PatchCyril Hrubis
1/3R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

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_PATH it'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_ or ltp_ rather than TST_ or tst_...

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]