From: Andrew Morton <akpm@linux-foundation•org>
To: Mark Brown <broonie@kernel•org>
Cc: Bala-Vignesh-Reddy <reddybalavignesh9979@gmail•com>,
Wei Yang <richard.weiyang@gmail•com>,
David Hildenbrand <david@redhat•com>,
"David S. Miller" <davem@davemloft•net>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the mm-nonmm-unstable tree
Date: Fri, 17 Oct 2025 14:34:55 -0700 [thread overview]
Message-ID: <20251017143455.712b94e1cfa744fa7a46215e@linux-foundation.org> (raw)
In-Reply-To: <aPJD4ANRWUDVDqKc@sirena.org.uk>
On Fri, 17 Oct 2025 14:25:52 +0100 Mark Brown <broonie@kernel•org> wrote:
> After merging the mm-nonmm-unstable tree, today's linux-next build
> (x86 allmodconfig) failed like this:
>
> In file included from /tmp/next/build/samples/vfs/test-list-all-mounts.c:11:
> /tmp/next/build/samples/vfs/../../tools/testing/selftests/pidfd/pidfd.h:28:10: fatal error: kselftest.h: No such file or directory
> 28 | #include "kselftest.h"
> | ^~~~~~~~~~~~~
Well that:
#include "../../tools/testing/selftests/pidfd/pidfd.h"
was a strange thing to do.
I'll toss this on top:
--- a/samples/vfs/Makefile~selftests-complete-kselftest-include-centralization-fix
+++ a/samples/vfs/Makefile
@@ -1,4 +1,6 @@
# SPDX-License-Identifier: GPL-2.0-only
userprogs-always-y += test-fsmount test-statx mountinfo test-list-all-mounts
+CFLAGS += -I../../tools/testing/selftests
+
userccflags += -I usr/include
_
but there's probably a better way...
next prev parent reply other threads:[~2025-10-17 21:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 13:25 linux-next: build failure after merge of the mm-nonmm-unstable tree Mark Brown
2025-10-17 21:34 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-29 9:10 Thierry Reding
2026-03-17 14:32 Mark Brown
2026-03-17 15:06 ` Mathieu Desnoyers
2026-03-17 15:07 ` David CARLIER
2026-02-16 13:58 Mark Brown
2025-12-18 4:30 Stephen Rothwell
2025-12-21 2:58 ` Finn Thain
2025-12-26 16:45 ` Sasha Levin
2025-12-29 8:56 ` Finn Thain
2026-01-01 9:21 ` Finn Thain
2026-01-01 17:01 ` Randy Dunlap
2026-01-01 23:15 ` Finn Thain
2026-01-02 7:29 ` Ard Biesheuvel
2026-01-02 22:09 ` Finn Thain
2025-11-16 23:23 Stephen Rothwell
2025-11-19 23:14 ` Stephen Rothwell
2025-11-19 23:48 ` Andrew Morton
2025-11-20 8:55 ` Miguel Ojeda
2025-11-20 10:01 ` Alice Ryhl
2025-11-16 22:36 Stephen Rothwell
2025-09-01 1:17 Stephen Rothwell
2025-07-11 0:58 Stephen Rothwell
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=20251017143455.712b94e1cfa744fa7a46215e@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=broonie@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=david@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=reddybalavignesh9979@gmail$(echo .)com \
--cc=richard.weiyang@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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