Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: stable@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	patches@lists.linux.dev,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Shuah Khan <shuah@kernel.org>,
	linux-kselftest@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: [PATCH 6.1 756/885] selftests: membarrier: Fix incorrect kernel headers search path
Date: Tue,  7 Mar 2023 18:01:30 +0100	[thread overview]
Message-ID: <20230307170034.780947360@linuxfoundation.org> (raw)
In-Reply-To: <20230307170001.594919529@linuxfoundation.org>

From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>

commit 498bb027726371ba4a94686d251f9be1d437573e upstream.

Use $(KHDR_INCLUDES) as lookup path for kernel headers. This prevents
building against kernel headers from the build environment in scenarios
where kernel headers are installed into a specific output directory
(O=...).

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Shuah Khan <shuah@kernel.org>
Cc: linux-kselftest@vger.kernel.org
Cc: Ingo Molnar <mingo@redhat.com>
Cc: <stable@vger.kernel.org>  # 5.18+
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
 tools/testing/selftests/membarrier/Makefile |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/tools/testing/selftests/membarrier/Makefile
+++ b/tools/testing/selftests/membarrier/Makefile
@@ -1,5 +1,5 @@
 # SPDX-License-Identifier: GPL-2.0-only
-CFLAGS += -g -I../../../../usr/include/
+CFLAGS += -g $(KHDR_INCLUDES)
 LDLIBS += -lpthread
 
 TEST_GEN_PROGS := membarrier_test_single_thread \



  parent reply	other threads:[~2023-03-07 18:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230307170001.594919529@linuxfoundation.org>
2023-03-07 17:01 ` [PATCH 6.1 729/885] selftests: x86: Fix incorrect kernel headers search path Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 750/885] selftests: sched: " Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 751/885] selftests: core: " Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 752/885] selftests: pid_namespace: " Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 753/885] selftests: arm64: " Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 754/885] selftests: clone3: " Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 755/885] selftests: pidfd: " Greg Kroah-Hartman
2023-03-07 17:01 ` Greg Kroah-Hartman [this message]
2023-03-07 17:01 ` [PATCH 6.1 757/885] selftests: kcmp: " Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 758/885] selftests: media_tests: " Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 759/885] selftests: gpio: " Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 760/885] selftests: filesystems: " Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 761/885] selftests: user_events: " Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 762/885] selftests: ptp: " Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 763/885] selftests: sync: " Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 764/885] selftests: rseq: " Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 765/885] selftests: move_mount_set_group: " Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 766/885] selftests: mount_setattr: " Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 767/885] selftests: perf_events: " Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 768/885] selftests: ipc: " Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 769/885] selftests: futex: " Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 770/885] selftests: drivers: " Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 771/885] selftests: dmabuf-heaps: " Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 772/885] selftests: vm: " Greg Kroah-Hartman
2023-03-07 17:01 ` [PATCH 6.1 773/885] selftests: seccomp: " Greg Kroah-Hartman

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=20230307170034.780947360@linuxfoundation.org \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@redhat.com \
    --cc=patches@lists.linux.dev \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    /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