From: Bala-Vignesh-Reddy <reddybalavignesh9979@gmail.com>
To: akpm@linux-foundation.org
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
shuah@kernel.org, richard.weiyang@gmail.com, lkp@intel.com,
reddybalavignesh9979@gmail.com,
linux-kernel-mentees@lists.linux.dev
Subject: [PATCH] samples/vfs: add selftests include path for kselftest.h
Date: Fri, 17 Oct 2025 14:32:01 +0530 [thread overview]
Message-ID: <20251017090201.317521-1-reddybalavignesh9979@gmail.com> (raw)
In-Reply-To: <20251016104409.68985-1-reddybalavignesh9979@gmail.com>
The test-list-all-mounts sample includes pidfd.h from selftests,
which now uses the centralized kselftest.h include after the
previous change. Add the selftests directory to the include path
so the build can find kselftest.h
This fixes a build error reported by the kernel test robot.
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202510171513.6IWk005g-lkp@intel.com/
Signed-off-by: Bala-Vignesh-Reddy <reddybalavignesh9979@gmail.com>
---
samples/vfs/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/samples/vfs/Makefile b/samples/vfs/Makefile
index 6554b73a75c8..9256ca5d762b 100644
--- a/samples/vfs/Makefile
+++ b/samples/vfs/Makefile
@@ -1,4 +1,5 @@
# SPDX-License-Identifier: GPL-2.0-only
userprogs-always-y += test-fsmount test-statx mountinfo test-list-all-mounts
+userccflags += -I $(srctree)/tools/testing/selftests/
userccflags += -I usr/include
--
2.43.0
next prev parent reply other threads:[~2025-10-17 9:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250830163949.20952-1-reddybalavignesh9979@gmail.com>
2025-10-16 10:44 ` [PATCH v3] selftests: complete kselftest include centralization Bala-Vignesh-Reddy
2025-10-17 9:02 ` Bala-Vignesh-Reddy [this message]
2026-01-06 12:29 ` Brendan Jackman
2026-01-10 16:00 ` Bala-Vignesh-Reddy
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=20251017090201.317521-1-reddybalavignesh9979@gmail.com \
--to=reddybalavignesh9979@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkp@intel.com \
--cc=richard.weiyang@gmail.com \
--cc=shuah@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