All of lore.kernel.org
 help / color / mirror / Atom feed

diff for duplicates of <20170427075825.GB4706@dhcp22.suse.cz>

diff --git a/a/1.txt b/N1/1.txt
index b3cb4fe..5a2dd8a 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,43 +1,2 @@
 I plan to fold the following into this patch.
----
->From 2cdb8e398eaeddf8b743bddb421dc5d9e49e442d Mon Sep 17 00:00:00 2001
-From: Michal Hocko <mhocko@suse.com>
-Date: Thu, 27 Apr 2017 09:53:01 +0200
-Subject: [PATCH] fold me "mm: consider zone which is not fully populated to
- have holes"
-
-- clarify pfn_valid semantic - requested by Joonsoo
----
- include/linux/mmzone.h | 13 +++++++++----
- 1 file changed, 9 insertions(+), 4 deletions(-)
-
-diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
-index aa8cc03287b0..f8c9453635e5 100644
---- a/include/linux/mmzone.h
-+++ b/include/linux/mmzone.h
-@@ -1268,10 +1268,15 @@ unsigned long __init node_memmap_size_bytes(int, unsigned long, unsigned long);
- #ifdef CONFIG_ARCH_HAS_HOLES_MEMORYMODEL
- /*
-  * pfn_valid() is meant to be able to tell if a given PFN has valid memmap
-- * associated with it or not. In FLATMEM, it is expected that holes always
-- * have valid memmap as long as there is valid PFNs either side of the hole.
-- * In SPARSEMEM, it is assumed that a valid section has a memmap for the
-- * entire section.
-+ * associated with it or not. This means that a struct page exists for this
-+ * pfn. The caller cannot assume the page is fully initialized in general.
-+ * Hotplugable pages might not have been onlined yet. pfn_to_online_page()
-+ * will ensure the struct page is fully online and initialized. Special pages
-+ * (e.g. ZONE_DEVICE) are never onlined and should be treated accordingly.
-+ *
-+ * In FLATMEM, it is expected that holes always have valid memmap as long as
-+ * there is valid PFNs either side of the hole. In SPARSEMEM, it is assumed
-+ * that a valid section has a memmap for the entire section.
-  *
-  * However, an ARM, and maybe other embedded architectures in the future
-  * free memmap backing holes to save memory on the assumption the memmap is
--- 
-2.11.0
-
--- 
-Michal Hocko
-SUSE Labs
\ No newline at end of file
+---
\ No newline at end of file
diff --git a/a/content_digest b/N1/content_digest
index 3bc49a5..d14f360 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -43,48 +43,7 @@
 ]
 [
   "I plan to fold the following into this patch.\n",
-  "---\n",
-  ">From 2cdb8e398eaeddf8b743bddb421dc5d9e49e442d Mon Sep 17 00:00:00 2001\n",
-  "From: Michal Hocko <mhocko\@suse.com>\n",
-  "Date: Thu, 27 Apr 2017 09:53:01 +0200\n",
-  "Subject: [PATCH] fold me \"mm: consider zone which is not fully populated to\n",
-  " have holes\"\n",
-  "\n",
-  "- clarify pfn_valid semantic - requested by Joonsoo\n",
-  "---\n",
-  " include/linux/mmzone.h | 13 +++++++++----\n",
-  " 1 file changed, 9 insertions(+), 4 deletions(-)\n",
-  "\n",
-  "diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h\n",
-  "index aa8cc03287b0..f8c9453635e5 100644\n",
-  "--- a/include/linux/mmzone.h\n",
-  "+++ b/include/linux/mmzone.h\n",
-  "\@\@ -1268,10 +1268,15 \@\@ unsigned long __init node_memmap_size_bytes(int, unsigned long, unsigned long);\n",
-  " #ifdef CONFIG_ARCH_HAS_HOLES_MEMORYMODEL\n",
-  " /*\n",
-  "  * pfn_valid() is meant to be able to tell if a given PFN has valid memmap\n",
-  "- * associated with it or not. In FLATMEM, it is expected that holes always\n",
-  "- * have valid memmap as long as there is valid PFNs either side of the hole.\n",
-  "- * In SPARSEMEM, it is assumed that a valid section has a memmap for the\n",
-  "- * entire section.\n",
-  "+ * associated with it or not. This means that a struct page exists for this\n",
-  "+ * pfn. The caller cannot assume the page is fully initialized in general.\n",
-  "+ * Hotplugable pages might not have been onlined yet. pfn_to_online_page()\n",
-  "+ * will ensure the struct page is fully online and initialized. Special pages\n",
-  "+ * (e.g. ZONE_DEVICE) are never onlined and should be treated accordingly.\n",
-  "+ *\n",
-  "+ * In FLATMEM, it is expected that holes always have valid memmap as long as\n",
-  "+ * there is valid PFNs either side of the hole. In SPARSEMEM, it is assumed\n",
-  "+ * that a valid section has a memmap for the entire section.\n",
-  "  *\n",
-  "  * However, an ARM, and maybe other embedded architectures in the future\n",
-  "  * free memmap backing holes to save memory on the assumption the memmap is\n",
-  "-- \n",
-  "2.11.0\n",
-  "\n",
-  "-- \n",
-  "Michal Hocko\n",
-  "SUSE Labs"
+  "---"
 ]
 
-84f40cd10551e09c0b20e6cd7950f2987ea5f84d82b8a1a6e614434d7be309e7
+33473190285b9d539d275126a249a7d2bb2eb52a8af25c216a3b370a6a55cd40
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.