mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Shuah Khan <shuah@kernel.org>
Cc: Baoquan He <baoquan.he@linux.dev>,
	kexec@lists.infradead.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH] selftests/kexec: don't fail the build on other architectures
Date: Wed,  4 Nov 2026 14:36:37 -0500	[thread overview]
Message-ID: <20261104193637.333158-1-sashal@kernel.org> (raw)

The kexec tests are only built for x86 and ppc64le. On other
architectures the Makefile defines no rules, so building or installing
the suite fails:

  make[1]: *** No targets.  Stop.

Give the Makefile empty targets there, as sparc64 and
drivers/s390x/uvdevice do, so that the suite builds and installs
nothing.

Fixes: a802ed0dd9c2 ("selftests/ima: kexec_load syscall test")
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
Found with KernelCI-style TuxMake builds that record per-suite results
with KSFT_BUILD_REPORT. x86_64 builds don't change, and arm64 and arm
builds now succeed without installing anything.

With ARCH=powerpc, as passed by the kernel's kselftest targets and by
CI, the ppc64le check doesn't match either, so the tests are only built
on powerpc when ARCH is taken from uname -m. This patch leaves that
alone.

 tools/testing/selftests/kexec/Makefile | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/tools/testing/selftests/kexec/Makefile b/tools/testing/selftests/kexec/Makefile
index 874cfdd3b75b3..11b30d49a7f23 100644
--- a/tools/testing/selftests/kexec/Makefile
+++ b/tools/testing/selftests/kexec/Makefile
@@ -17,4 +17,8 @@ endif
 
 include ../lib.mk
 
+else
+nothing:
+.PHONY: all clean run_tests install
+.SILENT:
 endif
-- 
2.53.0


                 reply	other threads:[~2026-11-04 19:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261104193637.333158-1-sashal@kernel.org \
    --to=sashal@kernel.org \
    --cc=baoquan.he@linux.dev \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®