From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] doc: Add ground rules page
Date: Tue, 9 Dec 2025 20:38:04 +0100 [thread overview]
Message-ID: <20251209193804.GB20883@pevik> (raw)
In-Reply-To: <aThHKguxntl-ZJBb@yuki.lan>
Hi all,
> Hi!
> > I don't recall if we have it mentioned already, but we also used to say that
> > changes introduced in early kernel -rc builds were low priority for acceptance
> > and we favored behavior that is in a released kernel (or at least in last -rcs).
> Sounds good.
+1. We could also mention runtest/staging
:master:`runtest/staging`, which we use for tests written against -rc kernels.
(So far we had only fanotify23 there, which was of course later migrated to
syscalls.)
> Also we probably need something along the lines:
> 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
done by :master:`configure.ac` script, ...
> useful for enabling fallback kernel API definitions when missing, as we
> do in lapi/ directory.
do in :master:`include/lapi/`.
Also about my previous note about referencing TST_CHECKPOINT_WAIT(), I know this
is a high level document, but IMHO linking helps newcomers.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-12-09 19:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 12:02 [LTP] [PATCH] doc: Add ground rules page Cyril Hrubis
2025-12-09 13:21 ` Jan Stancek via ltp
2025-12-09 15:58 ` Cyril Hrubis
2025-12-09 19:38 ` Petr Vorel [this message]
2025-12-09 19:31 ` 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=20251209193804.GB20883@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.