[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241031104247.65c76c00@canb.auug.org.au>
Date: Thu, 31 Oct 2024 10:42:47 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Catalin Marinas <catalin.marinas@....com>, Will Deacon
<will@...nel.org>, Andrew Morton <akpm@...ux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
Mailing List <linux-next@...r.kernel.org>, Lorenzo Stoakes
<lorenzo.stoakes@...cle.com>, Yang Shi <yang@...amperecomputing.com>
Subject: linux-next: manual merge of the arm64 tree with the mm-hotfixes
tree
Hi all,
Today's linux-next merge of the arm64 tree got a conflict in:
arch/arm64/include/asm/mman.h
between commit:
5af5d93e04c1 ("mm: refactor arch_calc_vm_flag_bits() and arm64 MTE handling")
from the mm-hotfixes-unstable branch of the mm-hotfixes tree and commit:
25c17c4b55de ("hugetlb: arm64: add mte support")
from the arm64 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.
--
Cheers,
Stephen Rothwell
diff --cc arch/arm64/include/asm/mman.h
index 798d965760d4,1dbfb56cb313..000000000000
--- a/arch/arm64/include/asm/mman.h
+++ b/arch/arm64/include/asm/mman.h
@@@ -42,7 -39,7 +42,7 @@@ static inline unsigned long arch_calc_v
* filesystem supporting MTE (RAM-based).
*/
if (system_supports_mte() &&
- ((flags & MAP_ANONYMOUS) || shmem_file(file)))
- (flags & (MAP_ANONYMOUS | MAP_HUGETLB)))
++ ((flags & (MAP_ANONYMOUS | MAP_HUGETLB)) || shmem_file(file)))
return VM_MTE_ALLOWED;
return 0;
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists