From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH 3/9] doc: Clarify API coverage and navigation
Date: Thu, 10 Sep 2026 21:52:57 +0200 [thread overview]
Message-ID: <20260910195257.GB270563@pevik> (raw)
In-Reply-To: <20260910-fix_documentation-v1-3-44313069bbe8@suse.com>
Hi Andrea,
> +++ b/doc/developers/api_network_tests.rst
> @@ -1,7 +1,31 @@
> .. SPDX-License-Identifier: GPL-2.0-or-later
> -.. Include headers in this file with:
> -.. .. kernel-doc:: ../../include/tst_test.h
Yeah, the docs is now kind of obvious.
> -
> Developing using network API
> ============================
> +
> +Overview
> +--------
> +
> +LTP network tests support both single-host and two-host test configurations.
nit: Maybe blank line here (it's own paragraph). But even this is going to lead
to duplicity (functionality described in both places).
> +Network stress tests and environment parameters are defined in
These variables are also for other network tests than just stress tests.
> +:shell_lib:`tst_net.sh` and documented in
> +:master:`testcases/network/README.md`.
The above is ok, but I would just point:
Network tests are documented in :master:`testcases/network/README.md`.
and delete the rest of the docs below ...
> +
> +Single-host configuration
> +~~~~~~~~~~~~~~~~~~~~~~~~~
... because this Single-host and Two-host related sections is a duplicity of
testcases/network/README.md. I'm ok to move testcases/network/README.md to
readthedocs, but it should not be on 2 places. I recently spent time to remove
doc duplicity, because sooner or later one of them gets outdated, please don't
introduce it again.
The other unrelated changes are ok (feel free to add my RBT for them if in a
separate commit).
Kind regards,
Petr
> +
> +Single-host is the default configuration when the ``RHOST`` environment
> +variable is not defined. LTP creates an ``ltp_ns`` network namespace and
> +configures a ``veth`` pair according to LTP network environment variables.
> +
> +Two-host configuration
> +~~~~~~~~~~~~~~~~~~~~~~
> +
> +This setup requires the ``RHOST`` environment variable to be set to the
> +hostname or IP address of the remote test machine, along with passwordless
> +SSH access configured for root. Both machines must have LTP installed in
> +the same location.
> +
> +For more details on network test setup, server service dependencies, and
> +running the tests with ``network.sh``, see
> +:master:`testcases/network/README.md`.
...
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-09-10 19:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 8:33 [LTP] [PATCH 0/9] doc: Improve and fix documentation and API comments Andrea Cervesato
2026-09-10 8:33 ` [LTP] [PATCH 1/9] doc: Fix examples and generated links Andrea Cervesato
2026-09-10 10:47 ` [LTP] " linuxtestproject.agent
2026-09-10 19:07 ` [LTP] [PATCH 1/9] " Petr Vorel
2026-09-10 8:33 ` [LTP] [PATCH 2/9] doc: Correct guide and API descriptions Andrea Cervesato
2026-09-10 19:32 ` Petr Vorel
2026-09-10 8:33 ` [LTP] [PATCH 3/9] doc: Clarify API coverage and navigation Andrea Cervesato
2026-09-10 19:52 ` Petr Vorel [this message]
2026-09-11 6:57 ` Andrea Cervesato via ltp
2026-09-10 8:33 ` [LTP] [PATCH 4/9] include: Document assertion API macros Andrea Cervesato
2026-09-10 8:33 ` [LTP] [PATCH 5/9] include: Document filesystem test utilities Andrea Cervesato
2026-09-10 8:33 ` [LTP] [PATCH 6/9] include: Document memory " Andrea Cervesato
2026-09-10 8:33 ` [LTP] [PATCH 7/9] include: Document safe file operations Andrea Cervesato
2026-09-10 8:33 ` [LTP] [PATCH 8/9] doc: Document CPU and common test helpers Andrea Cervesato
2026-09-10 8:33 ` [LTP] [PATCH 9/9] include: Fix API comment spelling and style Andrea Cervesato
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=20260910195257.GB270563@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.de \
--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 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.