From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/2] doc/user-guide: Improve LTPROOT docs
Date: Fri, 14 Jan 2022 20:44:43 +0100 [thread overview]
Message-ID: <20220114194444.16949-2-pvorel@suse.cz> (raw)
In-Reply-To: <20220114194444.16949-1-pvorel@suse.cz>
Signed-off-by: Petr Vorel <pvorel@suse.cz>
---
doc/user-guide.txt | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/doc/user-guide.txt b/doc/user-guide.txt
index b1ab13832e..5f5a86c9d0 100644
--- a/doc/user-guide.txt
+++ b/doc/user-guide.txt
@@ -11,7 +11,9 @@ For running LTP network tests see `testcases/network/README.md`.
| 'KCONFIG_PATH' | The path to the kernel config file, (if not set, it tries
the usual paths '/boot/config-RELEASE' or '/proc/config.gz').
| 'KCONFIG_SKIP_CHECK' | Skip kernel config check if variable set (not set by default).
-| 'LTPROOT' | Prefix for installed LTP, the default is '/opt/ltp'.
+| 'LTPROOT' | Prefix for installed LTP. **Should be always set**
+ as some tests need it for path to test data files
+ ('LTP_DATAROOT'). LTP is by default installed into '/opt/ltp'.
| 'LTP_COLORIZE_OUTPUT' | Force colorized output behaviour. 'y' or '1': always colorize
'n' or '0': never colorize.
| 'LTP_DEV' | Path to the block device to be used
--
2.34.1
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-01-14 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 19:44 [LTP] [PATCH 0/2] Improve user variable docs Petr Vorel
2022-01-14 19:44 ` Petr Vorel [this message]
2022-01-24 15:02 ` [LTP] [PATCH 1/2] doc/user-guide: Improve LTPROOT docs Cyril Hrubis
2022-01-14 19:44 ` [LTP] [PATCH 2/2] doc/user-guide: Remove "2. Colorized output" section Petr Vorel
2022-01-17 3:58 ` Li Wang
2022-01-24 15:02 ` Cyril Hrubis
2022-01-24 17:19 ` Petr Vorel
2022-01-24 21:18 ` 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=20220114194444.16949-2-pvorel@suse.cz \
--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