From: Andrew Morton <akpm@linux-foundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Shuah Khan <shuah@kernel.org>,
Aleksei Oladko <aleksey.oladko@virtuozzo.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/prctl: select the tests by ARCH alone
Date: Wed, 4 Nov 2026 12:08:59 -0800 [thread overview]
Message-ID: <20261104120859.28099ada5f1dbce682cb6267@linux-foundation.org> (raw)
In-Reply-To: <20261104193639.333186-1-sashal@kernel.org>
On Wed, 4 Nov 2026 14:36:39 -0500 Sasha Levin <sashal@kernel.org> wrote:
> The prctl tests are only built for x86, and only when CROSS_COMPILE is
> not set. In every other case the Makefile defines no rules, so building
> or installing the suite fails:
>
> make[1]: *** No targets. Stop.
>
> TuxMake sets CROSS_COMPILE for every build, native x86_64 ones
> included, so CI systems that use it, such as KernelCI, see prctl fail
> on every architecture and never build its tests.
>
> Like breakpoints, ipc and x86, decide by ARCH alone whether the tests
> are built, and give the Makefile empty targets on other architectures,
> as sparc64 and drivers/s390x/uvdevice do, so that the suite builds and
> installs nothing there.
Well that's annoying, but...
Rather than continuing to make this selftest x86-only, wouldn't it be
better to fix things up so the other architectures also benefit?
In fact someone proposed doing that just last month. Oh, it was you ;)
https://lore.kernel.org/20261014200127.1363472-1-sashal@kernel.org
what happened to that?
next prev parent reply other threads:[~2026-11-04 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 19:36 Sasha Levin
2026-11-04 20:08 ` Andrew Morton [this message]
2026-11-04 22:39 ` Sasha Levin
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=20261104120859.28099ada5f1dbce682cb6267@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aleksey.oladko@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=sashal@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®