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 08:23:17 +0200 [thread overview]
Message-ID: <ap5WKkAd5WBJhAsj@windsurf> (raw)
In-Reply-To: <20260905093953.62996-1-maxime.chevallier@bootlin.com>
Hello Maxime,
On Sat, Sep 05, 2026 at 11:39:51AM +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.
But then doesn't that mean that the build would be broken for people
who build Linux < 6.7 ? Keep in mind that the Linux kernel version in
Buildroot is configurable, so not everyone is building the latest and
greatest.
If that's the case, then maybe we need to keep both?
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 6:23 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 [this message]
2026-09-07 6:54 ` Maxime Chevallier via buildroot
2026-09-07 8:12 ` Thomas Petazzoni via buildroot
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=ap5WKkAd5WBJhAsj@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