From: Siddharth Menon <simeddon@gmail.com>
To: simeddon@gmail.com, jpoimboe@kernel.org, jikos@kernel.org,
mbenes@suse.cz, pmladek@suse.com, shuah@kernel.org
Cc: live-patching@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: [PATCH 3/3] selftests/livepatch: Check if required config options are enabled
Date: Thu, 5 Dec 2024 17:17:57 +0530 [thread overview]
Message-ID: <20241205114757.5916-4-simeddon@gmail.com> (raw)
In-Reply-To: <20241205114757.5916-1-simeddon@gmail.com>
When CONFIG_LIVEPATCH is disabled, compilation fails due to the
required structs from the livepatch header file being undefined.
This checks for whether CONFIG_LIVEPATCH and CONFIG_DYNAMIC_DEBUG
are enabled before compiling livepatch self-tests.
Signed-off-by: Siddharth Menon <simeddon@gmail.com>
---
tools/testing/selftests/livepatch/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/livepatch/Makefile b/tools/testing/selftests/livepatch/Makefile
index a080eb54a215..14b5c60663cd 100644
--- a/tools/testing/selftests/livepatch/Makefile
+++ b/tools/testing/selftests/livepatch/Makefile
@@ -14,5 +14,6 @@ TEST_PROGS := \
test-kprobe.sh
TEST_FILES := settings
+TEST_CONFIG_DEPS := CONFIG_LIVEPATCH CONFIG_DYNAMIC_DEBUG
include ../lib.mk
--
2.39.5
prev parent reply other threads:[~2024-12-05 11:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 11:47 [PATCH 0/3] kselftest framework to introduce TEST_CONFIG_DEPS Siddharth Menon
2024-12-05 11:47 ` [PATCH 1/3] docs/kselftests: Explain the usage of TEST_CONFIG_DEPS Siddharth Menon
2024-12-10 14:30 ` Petr Mladek
2024-12-05 11:47 ` [PATCH 2/3] selftests/lib.mk: Introduce check to validate required configs Siddharth Menon
2024-12-05 15:35 ` Mark Brown
2024-12-06 19:20 ` BiscuitBobby
2024-12-06 19:50 ` Mark Brown
2024-12-06 20:12 ` BiscuitBobby
2024-12-10 14:56 ` Petr Mladek
2024-12-10 17:10 ` BiscuitBobby
2024-12-12 9:02 ` Petr Mladek
2024-12-05 11:47 ` Siddharth Menon [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=20241205114757.5916-4-simeddon@gmail.com \
--to=simeddon@gmail.com \
--cc=jikos@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
--cc=shuah@kernel.org \
/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.