* linux-next: manual merge of the sh tree with the mm-unstable tree
@ 2023-04-17 12:20 broonie
0 siblings, 0 replies; 2+ messages in thread
From: broonie @ 2023-04-17 12:20 UTC (permalink / raw)
To: John Paul Adrian Glaubitz
Cc: Andrew Morton, Linux Kernel Mailing List,
Linux Next Mailing List, Peter Xu, Randy Dunlap
Hi all,
Today's linux-next merge of the sh tree got a conflict in:
tools/testing/selftests/mm/Makefile
between commit:
aaf87fd8703a5 ("selftests/mm: use TEST_GEN_PROGS where proper")
from the mm-unstable tree and commit:
644a9cf0d2a83 ("sh: remove sh5/sh64 last fragments")
from the sh 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 --git a/tools/testing/selftests/mm/Makefile b/tools/testing/selftests/mm/Makefile
index a913397c6b3c5..3ad614d359e44 100644
--- a/tools/testing/selftests/mm/Makefile
+++ b/tools/testing/selftests/mm/Makefile
@@ -93,7 +93,7 @@ endif
endif
-ifneq (,$(filter $(MACHINE),arm64 ia64 mips64 parisc64 ppc64 riscv64 s390x sh64 sparc64 x86_64))
+ifneq (,$(filter $(MACHINE),arm64 ia64 mips64 parisc64 ppc64 riscv64 s390x sparc64 x86_64))
TEST_GEN_PROGS += va_high_addr_switch
TEST_GEN_PROGS += virtual_address_range
TEST_GEN_PROGS += write_to_hugetlbfs
^ permalink raw reply related [flat|nested] 2+ messages in thread
* linux-next: manual merge of the sh tree with the mm-unstable tree
@ 2023-04-13 13:58 broonie
0 siblings, 0 replies; 2+ messages in thread
From: broonie @ 2023-04-13 13:58 UTC (permalink / raw)
To: John Paul Adrian Glaubitz
Cc: Andrew Morton, Linux Kernel Mailing List,
Linux Next Mailing List, Peter Xu, Randy Dunlap
Hi all,
Today's linux-next merge of the sh tree got a conflict in:
tools/testing/selftests/mm/Makefile
between commit:
14940f545c315 ("selftests/mm: use TEST_GEN_PROGS where proper")
from the mm-unstable tree and commit:
644a9cf0d2a83 ("sh: remove sh5/sh64 last fragments")
from the sh 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/mm/Makefile
index 5a34344194035,fc35050b5542f..0000000000000
--- a/tools/testing/selftests/mm/Makefile
+++ b/tools/testing/selftests/mm/Makefile
@@@ -93,10 -90,10 +93,10 @@@ endi
endif
- ifneq (,$(filter $(MACHINE),arm64 ia64 mips64 parisc64 ppc64 riscv64 s390x sh64 sparc64 x86_64))
+ ifneq (,$(filter $(MACHINE),arm64 ia64 mips64 parisc64 ppc64 riscv64 s390x sparc64 x86_64))
-TEST_GEN_FILES += va_128TBswitch
-TEST_GEN_FILES += virtual_address_range
-TEST_GEN_FILES += write_to_hugetlbfs
+TEST_GEN_PROGS += va_128TBswitch
+TEST_GEN_PROGS += virtual_address_range
+TEST_GEN_PROGS += write_to_hugetlbfs
endif
TEST_PROGS := run_vmtests.sh
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-04-17 12:22 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-04-17 12:20 linux-next: manual merge of the sh tree with the mm-unstable tree broonie
-- strict thread matches above, loose matches on Subject: below --
2023-04-13 13:58 broonie
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).