From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/linux-tools: selftests: Use KHDR_INCLUDES to locate the headers
Date: Wed, 7 Oct 2026 09:57:21 +0200 [thread overview]
Message-ID: <asX7W8r75WzGv8jv@windsurf> (raw)
In-Reply-To: <20261004213116.39415-1-maxime.chevallier@bootlin.com>
On Sun, Oct 04, 2026 at 11:31:15PM +0200, Maxime Chevallier via buildroot wrote:
> Since v6.7 [1], the KHDR_DIR variable isn't used anymore by the kernel
> selftest Makefiles to locate the kernel headers. Instead, KHDR_INCLUDES
> is used to specify their location. It was only available between v6.5
> and v6.7.
>
> Keep KHDR_DIR for compatibility with v6.5 to v6.7 kernels, while
> KHDR_INCLUDES is used by both pre 6.5 and post 6.7 kernels.
>
> Let's pass it with the "-isystem" flag, as is done in the default values
> used in the selftest makefiles.
>
> [1]: 43e8832fed08 ("Revert "selftests: error out if kernel header files are not yet built"")
>
> Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
Applied to master, thanks!
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-10-07 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 21:31 [Buildroot] [PATCH v2] package/linux-tools: selftests: Use KHDR_INCLUDES to locate the headers Maxime Chevallier via buildroot
2026-10-07 7:57 ` Thomas Petazzoni via buildroot [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=asX7W8r75WzGv8jv@windsurf \
--to=buildroot@buildroot.org \
--cc=maxime.chevallier@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
/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