* linux-next: manual merge of the fs-next tree with the origin tree
@ 2026-09-04 18:11 Mark Brown
2026-09-04 18:35 ` Andrew Morton
0 siblings, 1 reply; 3+ messages in thread
From: Mark Brown @ 2026-09-04 18:11 UTC (permalink / raw)
Cc: Andrew Morton, Christian Brauner, Disha Goel,
Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]
Hi all,
Today's linux-next merge of the fs-next tree got a conflict in:
tools/testing/selftests/Makefile
between commit:
4ff32f084c158 ("selftests/filesystems: fix missing and stale TARGETS entries")
from the origin tree and commit:
5550456dad376 ("selftests/filesystems: Move file_stressor to dedicated subdirectory")
from the fs-next tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
diff --cc tools/testing/selftests/Makefile
index 330d061f6366f,08f228765a930..0000000000000
--- a/tools/testing/selftests/Makefile
+++ b/tools/testing/selftests/Makefile
@@@ -35,11 -35,9 +35,12 @@@ TARGETS += fchmodat
TARGETS += filesystems
TARGETS += filesystems/binderfs
TARGETS += filesystems/epoll
+TARGETS += filesystems/eventfd
TARGETS += filesystems/failfs
TARGETS += filesystems/fat
+ TARGETS += filesystems/file_stressor
+TARGETS += filesystems/openat2
+TARGETS += filesystems/open_tree_ns
TARGETS += filesystems/overlayfs
TARGETS += filesystems/statmount
TARGETS += filesystems/mount-notify
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: manual merge of the fs-next tree with the origin tree
2026-09-04 18:11 linux-next: manual merge of the fs-next tree with the origin tree Mark Brown
@ 2026-09-04 18:35 ` Andrew Morton
2026-09-04 18:42 ` Mark Brown
0 siblings, 1 reply; 3+ messages in thread
From: Andrew Morton @ 2026-09-04 18:35 UTC (permalink / raw)
To: Mark Brown
Cc: Christian Brauner, Disha Goel, Linux Kernel Mailing List,
Linux Next Mailing List
On Fri, 4 Sep 2026 19:11:24 +0100 Mark Brown <broonie@kernel.org> wrote:
> Hi all,
>
> Today's linux-next merge of the fs-next tree got a conflict in:
>
> tools/testing/selftests/Makefile
>
> between commit:
>
> 4ff32f084c158 ("selftests/filesystems: fix missing and stale TARGETS entries")
>
> from the origin tree and commit:
"origin tree"? I assume mm.git's mm-nonmm-unstable was intended.
>
> 5550456dad376 ("selftests/filesystems: Move file_stressor to dedicated subdirectory")
>
> from the fs-next tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
OK, thanks. I'll send "selftests/filesystems: fix missing and stale
TARGETS entries" over to Christian.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: manual merge of the fs-next tree with the origin tree
2026-09-04 18:35 ` Andrew Morton
@ 2026-09-04 18:42 ` Mark Brown
0 siblings, 0 replies; 3+ messages in thread
From: Mark Brown @ 2026-09-04 18:42 UTC (permalink / raw)
To: Andrew Morton
Cc: Christian Brauner, Disha Goel, Linux Kernel Mailing List,
Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 507 bytes --]
On Fri, Sep 04, 2026 at 11:35:58AM -0700, Andrew Morton wrote:
> On Fri, 4 Sep 2026 19:11:24 +0100 Mark Brown <broonie@kernel.org> wrote:
> > Today's linux-next merge of the fs-next tree got a conflict in:
> > tools/testing/selftests/Makefile
> > between commit:
> > 4ff32f084c158 ("selftests/filesystems: fix missing and stale TARGETS entries")
> > from the origin tree and commit:
> "origin tree"? I assume mm.git's mm-nonmm-unstable was intended.
gitk wasn't picking that up for some reason.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-09-04 18:42 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-09-04 18:11 linux-next: manual merge of the fs-next tree with the origin tree Mark Brown
2026-09-04 18:35 ` Andrew Morton
2026-09-04 18:42 ` Mark Brown
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®