[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20190502191119.2707499f@canb.auug.org.au>
Date: Thu, 2 May 2019 19:11:19 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Andrew Morton <akpm@...ux-foundation.org>,
Helge Deller <deller@....de>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Christoph Hellwig <hch@....de>
Subject: linux-next: manual merge of the akpm-current tree with the
parisc-hd tree
Hi all,
Today's linux-next merge of the akpm-current tree got a conflict in:
arch/parisc/mm/init.c
between commit:
1fb55c4cf4e6 ("parisc: Enable SPARSEMEM_VMEMMAP")
from the parisc-hd tree and commit:
2e5adbd9e97a ("initramfs: provide a generic free_initrd_mem implementation")
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.
--
Cheers,
Stephen Rothwell
diff --cc arch/parisc/mm/init.c
index 6d29eb22d460,437d4c35c562..000000000000
--- a/arch/parisc/mm/init.c
+++ b/arch/parisc/mm/init.c
@@@ -927,18 -921,3 +927,11 @@@ void flush_tlb_all(void
spin_unlock(&sid_lock);
}
#endif
+
- #ifdef CONFIG_BLK_DEV_INITRD
- void free_initrd_mem(unsigned long start, unsigned long end)
- {
- free_reserved_area((void *)start, (void *)end, -1, "initrd");
- }
- #endif
-
+#if defined(CONFIG_SPARSEMEM_VMEMMAP)
+int __meminit vmemmap_populate(unsigned long vstart, unsigned long vend,
+ int node, struct vmem_altmap *altmap)
+{
+ return vmemmap_populate_basepages(vstart, vend, node);
+}
+#endif
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists