From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 2/2] doc: Add ground rules page
Date: Tue, 16 Dec 2025 12:01:51 +0100 [thread overview]
Message-ID: <20251216110151.GB307257@pevik> (raw)
In-Reply-To: <20251215124404.16395-2-chrubis@suse.cz>
Hi Cyril,
Few more notes.
...
> +Use runtime checks for kernel features
> +======================================
> +
> +What is and what isn't supported by kernel is determined by the version
> +and configuration of the kernel the systems is currently running on.
> +That especially means that any checks done during the compilation cannot
> +be used to assume features supported by the kernel the tests end up
> +running on. The compile time checks, done by configure script, are only
Also please use link to the script:
-running on. The compile time checks, done by configure script, are only
+running on. The compile time checks, done by :master:`configure.ac`, are only
> +useful for enabling fallback kernel API definitions when missing, as we
> +do in lapi/ directory.
And to the lapi directory:
-do in lapi/ directory.
+do in headers in :master:`include/lapi/`.
(I'm not sure whether you just overlooked it or you don't see it useful.)
> +Kernel features and RCs
> +=======================
> +
> +LTP tests or fixes for kernel changes that were not released yet can be posted
> +to the LTP list for a review but will not be be accepted until respective
> +kernel changes are released. Review of such changes is also considered to be
> +lower priority than rest of the changes. This is because kernel changes
> +especially in the early RC phase are volatile and could be changed or reverted.
I would personally mention staging runtest file, but maybe I overlook your
:master:`runtest/staging`
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-12-16 11:02 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 [this message]
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
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=20251216110151.GB307257@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