From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/linux-tools: selftests: Use KHDR_INCLUDES to locate the headers
Date: Mon, 7 Sep 2026 10:12:39 +0200 [thread overview]
Message-ID: <ap5xxEjbIUYUJMPa@windsurf> (raw)
In-Reply-To: <dd27b98c-64cc-41ec-8312-60286fdb6c71@bootlin.com>
Hello,
On Mon, Sep 07, 2026 at 08:54:33AM +0200, Maxime Chevallier wrote:
> Looking at the kernel history, the KHDR_DIR only existed between v6.4 and v6.7 :
>
> Added in v6.4 :
>
> 9fc96c7c19df ("selftests: error out if kernel header files are not yet built")
>
> Reverted in v6.7 :
>
> 43e8832fed08 ("Revert "selftests: error out if kernel header files are not yet built"")
>
> And it looks like even between that v6.4 and v6.7 window, KHDR_DIR is just used to
> populate KHDR_INCLUDES :
>
>
> tools/testing/selftests/lib.mk
>
> [...]
>
> KHDR_INCLUDES := -isystem $(KHDR_DIR)
Ah good, so your change would potentially work across all kernel
versions?
> So I think this should work even on kernels older than v6.7, I haven't
> tried though ;(
Can we give it a quick try, just to make sure?
> I can add these details in the commit log in a resend if you want,
That would be awesome, thanks!
Thomas
--
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
next prev parent reply other threads:[~2026-09-07 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 9:39 [Buildroot] [PATCH] package/linux-tools: selftests: Use KHDR_INCLUDES to locate the headers Maxime Chevallier via buildroot
2026-09-07 6:23 ` Thomas Petazzoni via buildroot
2026-09-07 6:54 ` Maxime Chevallier via buildroot
2026-09-07 8:12 ` Thomas Petazzoni via buildroot [this message]
2026-10-03 16:31 ` Thomas Petazzoni via buildroot
2026-10-03 21:29 ` Maxime Chevallier via buildroot
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=ap5xxEjbIUYUJMPa@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