From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] doc/ground_rules: Add Kernel features check rules
Date: Wed, 11 Mar 2026 10:12:44 +0100 [thread overview]
Message-ID: <20260311091244.GA90982@pevik> (raw)
In-Reply-To: <DGC5KMP8J1V7.ALUWBN4R82H1@suse.com>
Hi all,
> Hi!
> Is this patch still valid? Should we merge it with minor details as
> suggested?
I planned to merge this with change Li suggested [1]. But in a meanwhile Cyril
posted lib: tst_kconfig: Add runtime checks [2]. Once he finds time to merge it,
I should probably send v2 of this patch - update Li's suggestion:
- Tristate/module feature: If the functionality is controlled by a Kconfig of
type tristate (`tristate
<https://docs.kernel.org/kbuild/kconfig-language.html#menu-attributes>`_),
it might be built as a module. Modules can be absent or unloaded
at runtime,
so checking the Kconfig option alone isn’t enough. .needs_kconfigs,
requires to add additional kconfig checks to confirm the module is loaded.
Also, Cyril noted [3] on thermal test that using .supported_archs is also useful
to define which arch is targeted (when used with .needs_drivers/.needs_kconfigs,
which would be enough for detecting the functionality). Do we want to add it as
a rule?
- Test targeted to a certain architecture should always use .supported_archs
even if this is not necessary as a check because test already define
.needs_drivers/.needs_kconfigs.
And back to my question some time ago. Do we want to deprecate .needs_drivers,
when Cyril enhanced .needs_kconfigs? Do we even need it?
Kind regards,
Petr
> Kind regards,
[1] https://lore.kernel.org/ltp/CAEemH2fc_C_vGnKtbYqsMzMVKLSNLhCFWLGemSyVTWBzAATDCA@mail.gmail.com/
[2] https://patchwork.ozlabs.org/project/ltp/patch/20260205135724.23772-1-chrubis@suse.cz/
[3] https://lore.kernel.org/ltp/aa_0YkA4UKwhOjpi@yuki.lan/
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-03-11 9:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 8:01 [LTP] [PATCH 1/1] doc/ground_rules: Add Kernel features check rules Petr Vorel
2026-01-28 9:00 ` Li Wang via ltp
2026-01-28 12:45 ` Petr Vorel
2026-01-28 20:50 ` Petr Vorel
2026-01-29 7:24 ` Li Wang via ltp
2026-01-29 8:59 ` Cyril Hrubis
2026-02-11 13:05 ` Andrea Cervesato via ltp
2026-03-11 9:12 ` Petr Vorel [this message]
2026-03-11 9:15 ` 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=20260311091244.GA90982@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.com \
--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