public inbox for linux-kselftest@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
	"Shuah Khan" <shuah@kernel.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Vincenzo Frascino" <vincenzo.frascino@arm.com>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jason Gunthorpe <jgg@ziepe.ca>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests: always install UAPI headers to the correct directory
Date: Thu, 18 Sep 2025 12:06:56 -0600	[thread overview]
Message-ID: <53ec38e9-5ba2-4a5e-9bfb-ba43e411be7f@linuxfoundation.org> (raw)
In-Reply-To: <20250918-kselftest-uapi-out-of-tree-v1-1-f4434f28adcd@linutronix.de>

On 9/18/25 03:56, Thomas Weißschuh wrote:
> Currently the UAPI headers are always installed into the source directory.
> When building out-of-tree this doesn't work, as the include path will be
> wrong and it dirties the source tree, leading to complains by kbuild.
> 
> Make sure the 'headers' target installs the UAPI headers in the correctly.
> 
> The real target directory can come from multiple places. To handle them all
> extract the target directory from KHDR_INCLUDES.
> 
> Reported-by: Jason Gunthorpe <jgg@nvidia.com>
> Closes: https://lore.kernel.org/lkml/20250917153209.GA2023406@nvidia.com/
> Fixes: 1a59f5d31569 ("selftests: Add headers target")
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
> ---
>   tools/testing/selftests/lib.mk | 5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
> 

Applied to linux-kselftest next branch for Linux 6.18-rc1

thanks,
-- Shuah

      reply	other threads:[~2025-09-18 18:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-18  9:56 [PATCH] selftests: always install UAPI headers to the correct directory Thomas Weißschuh
2025-09-18 18:06 ` Shuah Khan [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=53ec38e9-5ba2-4a5e-9bfb-ba43e411be7f@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=thomas.weissschuh@linutronix.de \
    --cc=vincenzo.frascino@arm.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