[lkml]   [2020]   [Sep]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectlinux-next: manual merge of the akpm-current tree with the arm64 tree
Hi all,

Today's linux-next merge of the akpm-current tree got a conflict in:


between commit:

0178dc761368 ("arm64: mte: Use Normal Tagged attributes for the linear map")

from the arm64 tree and commit:

8e19cbb9528f ("arch, drivers: replace for_each_membock() with for_each_mem_range()")

from the akpm-current 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.

Stephen Rothwell

diff --cc arch/arm64/mm/mmu.c
index 087a844b4d26,64211436629d..000000000000
--- a/arch/arm64/mm/mmu.c
+++ b/arch/arm64/mm/mmu.c
@@@ -493,21 -483,10 +494,15 @@@ static void __init map_mem(pgd_t *pgdp

/* map all the memory banks */
- for_each_memblock(memory, reg) {
- phys_addr_t start = reg->base;
- phys_addr_t end = start + reg->size;
+ for_each_mem_range(i, &start, &end) {
if (start >= end)
- if (memblock_is_nomap(reg))
- continue;
- __map_memblock(pgdp, start, end, PAGE_KERNEL, flags);
+ /*
+ * The linear map must allow allocation tags reading/writing
+ * if MTE is present. Otherwise, it has the same attributes as
+ */
+ __map_memblock(pgdp, start, end, PAGE_KERNEL_TAGGED, flags);

[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2020-09-21 10:04    [W:0.058 / U:0.056 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site