From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Sasha Levin <sashal@kernel.org>
Cc: Willy Tarreau <w@1wt.eu>, Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/nolibc: use the configured kernel header directory
Date: Wed, 14 Oct 2026 22:55:48 +0200 [thread overview]
Message-ID: <d7bcc69c-088d-420c-b301-50b4a94366ac@t-8ch.de> (raw)
In-Reply-To: <20261014200142.1364761-1-sashal@kernel.org>
On 2026-10-14 16:01:42-0400, Sasha Levin wrote:
> The freestanding build hardcodes the source tree's usr/include even when
> selftests exports KHDR_INCLUDES for an output-directory build. Use the
> exported header location while preserving -nostdlib, -nostdinc and static
> linkage. GCC 14 and Clang 21 builds then find the generated UAPI headers.
>
> Fixes: eb1353110831 ("selftests/nolibc: integrate with kselftests")
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> ---
> tools/testing/selftests/nolibc/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks!
(...)
prev parent reply other threads:[~2026-10-14 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 20:01 Sasha Levin
2026-10-14 20:55 ` Thomas Weißschuh [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=d7bcc69c-088d-420c-b301-50b4a94366ac@t-8ch.de \
--to=linux@weissschuh.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=shuah@kernel.org \
--cc=w@1wt.eu \
/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®