From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3 1/2] doc: Document process_state
Date: Wed, 7 Jan 2026 12:31:55 +0100 [thread overview]
Message-ID: <20260107113155.GB753482@pevik> (raw)
In-Reply-To: <20260107111133.27041-2-chrubis@suse.cz>
Hi Cyril, Andrea,
more fixes needed:
> +++ b/include/tst_process_state.h
...
> */
> #define TST_PROCESS_STATE_WAIT(pid, state, msec_timeout) \
> tst_process_state_wait(__FILE__, __LINE__, NULL, \
> (pid), (state), (msec_timeout))
> -/*
> - * Check that a given pid is present on the system
> +/**
> + * TST_PROCESS_EXIT_WAIT() - Waits while pid is present on the system.
> + *
> + * Loops until `kill($PID, 0)` succeds or timeout is reached.
> + *
> + * @pid A process pid.
^ missing ':' here leads to "pid – undescribed" in generated doc,
see ./doc/html/developers/api_c_tests.html#macro-tst-process-exit-wait
@Andrea: I wish sphinx doc would warn about "undescribed" and I thought it did
in the past, but I don't see it.
Also we have too many (~ 220x) warnings:
"WARNING: duplicate label description, other instance in ..." it's not usable.
Any hint you could have look on it? If we solve this warning would get useful.
> + * @msec_timeout: A timeout for the wait.
> */
> #define TST_PROCESS_EXIT_WAIT(pid, msec_timeout) \
> tst_process_exit_wait((pid), (msec_timeout))
> -/*
> - * Waits for thread state change.
> +/**
> + * TST_THREAD_STATE_WAIT() - Waits for a thread state change.
> *
> - * The state is one of the following:
> + * Polls `/proc/self/task/$TID/state` for a thread state change.
> *
> - * R - running
> - * S - sleeping
> - * D - disk sleep
> - * T - stopped
> - * t - tracing stopped
> - * Z - zombie
> - * X - dead
> + * Possible thread states are the same as for TST_PROCESS_STATE_WAIT().
And here we have "undescribed" due not being described:
Parameters:
tid – undescribed
state – undescribed
msec_timeout – undescribed
See ./doc/html/developers/api_c_tests.html#macro-tst-thread-state-wait
Kind regards,
Petr
> */
> #define TST_THREAD_STATE_WAIT(tid, state, msec_timeout) \
> tst_thread_state_wait((tid), (state), (msec_timeout))
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-01-07 11:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 11:11 [LTP] [PATCH v3 0/2] Add ground rules doc page Cyril Hrubis
2026-01-07 11:11 ` [LTP] [PATCH v3 1/2] doc: Document process_state Cyril Hrubis
2026-01-07 11:31 ` Petr Vorel [this message]
2026-01-07 12:23 ` Andrea Cervesato via ltp
2026-01-07 15:05 ` Petr Vorel
2026-01-12 8:32 ` Petr Vorel
2026-01-07 11:11 ` [LTP] [PATCH v3 2/2] doc: Add ground rules page Cyril Hrubis
2026-01-07 13:00 ` Li Wang via ltp
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=20260107113155.GB753482@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@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