From: Mark Brown <broonie@kernel.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>,
Ben Copeland <benjamin.copeland@linaro.org>,
Shuah Khan <shuah@kernel.org>
Subject: Re: next-20250909: selftests/arm64/gcs/basic-gcs.c:390:30: error: use of undeclared identifier 'HWCAP_GCS'
Date: Fri, 12 Sep 2025 12:14:00 +0100 [thread overview]
Message-ID: <a1dc9839-ab45-4dd6-9eeb-4bbc35bf8d90@sirena.org.uk> (raw)
In-Reply-To: <b9b8b8cf-4920-4f9d-bcea-bea913058601@weissschuh.net>
[-- Attachment #1: Type: text/plain, Size: 453 bytes --]
On Fri, Sep 12, 2025 at 01:07:58PM +0200, Thomas Weißschuh wrote:
> The Makefile does *not* use -nostdinc, so the nolibc program probably finds the toolchain's glibc asm/hwcap.h.
> There also doesn't seem to be a static arm64 hwcap header in tools/include in the first place.
> I am still wondering how this works for the other tests.
make headers_install puts a copy in usr/include, probably we just need
to include that in the include path.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-09-12 11:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 19:18 Naresh Kamboju
2025-09-11 21:01 ` Mark Brown
2025-09-12 6:30 ` Thomas Weißschuh
2025-09-12 10:23 ` Naresh Kamboju
2025-09-12 10:49 ` Mark Brown
2025-09-12 10:57 ` Thomas Weißschuh
2025-09-12 11:07 ` Thomas Weißschuh
2025-09-12 11:14 ` Mark Brown [this message]
2025-09-15 9:23 ` Thomas Weißschuh
2025-09-15 19:14 ` Naresh Kamboju
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=a1dc9839-ab45-4dd6-9eeb-4bbc35bf8d90@sirena.org.uk \
--to=broonie@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=benjamin.copeland@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=dan.carpenter@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
--cc=shuah@kernel.org \
--cc=will@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®