From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 1/2] doc: Document process_state
Date: Tue, 6 Jan 2026 14:56:42 +0100 [thread overview]
Message-ID: <20260106135642.GA714081@pevik> (raw)
In-Reply-To: <aV0MQv3D3hjGZK2I@yuki.lan>
> Hi!
> > > > - * R - process is running
> > > > - * S - process is sleeping
> > > > - * D - process sleeping uninterruptibly
> > > > - * Z - zombie process
> > > > - * T - process is traced
> > > > + * Possible process states:
> > > Maybe: use link to https://man7.org/linux/man-pages/man1/ps.1.html ?
> > > -* Possible process states:
> > > +* Possible process states (see :man1:`ps`):
> > 1. We do not have man1 defined in exlinks in conf.py
> > 2. Even if added there exlinks does not seem work from documentation
> > generated from headers
> This actually works, once I fixed typo in the conf.py change.
+1
...
> > > * Z
> > Zombie process is described in the list.
> > > Also, do we want specify the process states in both TST_PROCESS_STATE_WAIT() and
> > > TST_THREAD_STATE_WAIT(), or just specify it in one and mention in the other that
> > > they specify it? (via :ref: or c:func:).
> > Again, none of the :ref: or c:func: is working in docs generate from
> > headers.
Maybe c:func: really works only in the headers. I have in my notes
:c:func:`tst_kvercmp()`. We already use in doc/* some :ref: e.g.
:ref:`struct tst_device` or :ref:`tst_brk`.
> And this one needs to be just TST_PROCESS_STATE_WAIT() to be processed
> as a link in headers.
Interesting. For me works only :c:func:`TST_PROCESS_STATE_WAIT()` or
:c:func:`tst_brk()` when adding it into random file (e.g.
doc/maintainers/patch_review.rst).
Anyway, thanks for taking care to link it.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-01-06 13:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 12:44 [LTP] [PATCH v2 1/2] doc: Document process_state Cyril Hrubis
2025-12-15 12:44 ` [LTP] [PATCH v2 2/2] doc: Add ground rules page Cyril Hrubis
2025-12-15 13:32 ` Li Wang via ltp
2025-12-15 14:03 ` Li Wang via ltp
2025-12-15 14:25 ` Anrea Cervesato via ltp
2025-12-15 14:30 ` Petr Vorel
2025-12-15 15:00 ` Andrea Cervesato via ltp
2025-12-16 7:07 ` Li Wang via ltp
2025-12-16 7:27 ` Li Wang via ltp
2025-12-16 10:11 ` Petr Vorel
2025-12-16 10:42 ` Li Wang via ltp
2025-12-16 11:08 ` Andrea Cervesato via ltp
2025-12-16 11:23 ` Li Wang via ltp
2025-12-16 11:23 ` Cyril Hrubis
2025-12-16 11:24 ` Li Wang via ltp
2025-12-21 10:30 ` Petr Vorel
2025-12-15 14:52 ` Andrea Cervesato via ltp
2025-12-16 10:54 ` Petr Vorel
2025-12-16 11:01 ` Petr Vorel
2025-12-16 11:27 ` [LTP] [PATCH v2 1/2] doc: Document process_state Petr Vorel
2026-01-06 12:47 ` Cyril Hrubis
2026-01-06 13:21 ` Cyril Hrubis
2026-01-06 13:56 ` Petr Vorel [this message]
2026-01-06 15:15 ` Cyril Hrubis
2026-01-07 7:46 ` 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=20260106135642.GA714081@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 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.