From: Shuah Khan <skhan@linuxfoundation.org>
To: Siddharth Menon <simeddon@gmail.com>,
linux-kselftest@vger.kernel.org, shuah@kernel.org
Cc: pmladek@suse.com, mbenes@suse.cz, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v3 0/2 RESEND] update kselftest framework to check for required configs
Date: Thu, 27 Feb 2025 09:51:23 -0700 [thread overview]
Message-ID: <083e94e0-dc37-4cdd-94a3-db258635a684@linuxfoundation.org> (raw)
In-Reply-To: <20250227053322.114215-1-simeddon@gmail.com>
On 2/26/25 22:29, Siddharth Menon wrote:
> Currently, kselftests does not have a generalised mechanism to skip
> compilation and run tests when required kernel configuration options
> are disabled.
Skipping compile by default is not what we want to do. Tests are
supposed to compile and run even when config options are not enabled.
There is something wrong if the test doesn't compile when a config
option isn't enabled in the kernel.
>
> This patch series adresses this issue by checking whether all required
> configs from selftest/<test>/config are enabled in the current kernel
>
> Siddharth Menon (2):
> selftests: Introduce script to validate required dependencies
> selftests/lib.mk: Introduce check to validate required dependencies
>
> .../testing/selftests/check_kselftest_deps.pl | 170 ++++++++++++++++++
> tools/testing/selftests/lib.mk | 15 +-
> 2 files changed, 183 insertions(+), 2 deletions(-)
> create mode 100755 tools/testing/selftests/check_kselftest_deps.pl
>
thanks,
-- Shuah
prev parent reply other threads:[~2025-02-27 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 5:29 [PATCH v3 0/2 RESEND] update kselftest framework to check for required configs Siddharth Menon
2025-02-27 5:29 ` [PATCH v3 1/2 RESEND] selftests: Introduce script to validate required dependencies Siddharth Menon
2025-02-27 5:29 ` [PATCH v3 2/2] selftests/lib.mk: Introduce check " Siddharth Menon
2025-02-27 16:51 ` Shuah Khan [this message]
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=083e94e0-dc37-4cdd-94a3-db258635a684@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
--cc=shuah@kernel.org \
--cc=simeddon@gmail.com \
/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