[merged mm-stable] mm-mm_initc-extend-init-unavailable-range-doc-info.patch removed from -mm tree

[merged mm-stable] mm-mm_initc-extend-init-unavailable-range-doc-info.patch removed from -mm tree

[Andrew Morton]

The quilt patch titled
     Subject: mm/mm_init.c: extend init unavailable range doc info
has been removed from the -mm tree.  Its filename was
     mm-mm_initc-extend-init-unavailable-range-doc-info.patch

This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

------------------------------------------------------
From: Serge Semin <fancer.lancer@gmail.com>
Subject: mm/mm_init.c: extend init unavailable range doc info
Date: Wed, 22 Nov 2023 21:24:03 +0300

Besides of the already described reasons the pages backended memory holes
might be persistent due to having memory mapped IO spaces behind those
ranges in the framework of flatmem kernel config.  Add such note to the
init_unavailable_range() method kdoc in order to point out to one more
reason of having the function executed for such regions.

[fancer.lancer@gmail.com: update per Mike]
  Link: https://lkml.kernel.org/r/20231202111855.18392-1-fancer.lancer@gmail.com
Link: https://lkml.kernel.org/r/20231122182419.30633-6-fancer.lancer@gmail.com
Signed-off-by: Serge Semin <fancer.lancer@gmail.com>
Reviewed-by: Mike Rapoport (IBM) <rppt@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 mm/mm_init.c |    1 +
 1 file changed, 1 insertion(+)

--- a/mm/mm_init.c~mm-mm_initc-extend-init-unavailable-range-doc-info
+++ a/mm/mm_init.c
@@ -796,6 +796,7 @@ overlap_memmap_init(unsigned long zone,
  * - physical memory bank size is not necessarily the exact multiple of the
  *   arbitrary section size
  * - early reserved memory may not be listed in memblock.memory
+ * - non-memory regions covered by the contigious flatmem mapping
  * - memory layouts defined with memmap= kernel parameter may not align
  *   nicely with memmap sections
  *
_

Patches currently in -mm which might be from fancer.lancer@gmail.com are