diff for duplicates of <44F7F376.4030203@kolumbus.fi> diff --git a/a/content_digest b/N1/content_digest index 362bd20..175b945 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -10,14 +10,14 @@ "Subject\0Re: [PATCH 4/6] Have x86_64 use add_active_range() and free_area_init_nodes\0" "Date\0Fri, 01 Sep 2006 11:46:46 +0300\0" "To\0Mel Gorman <mel@csn.ul.ie>\0" - "Cc\0akpm@osdl.org" + "Cc\0Keith Mannthey <kmannth@gmail.com>" + akpm@osdl.org tony.luck@intel.com - linuxppc-dev@ozlabs.org + Linux Memory Management List <linux-mm@kvack.org> ak@suse.de bob.picco@hp.com Linux Kernel Mailing List <linux-kernel@vger.kernel.org> - Linux Memory Management List <linux-mm@kvack.org> - " Keith Mannthey <kmannth@gmail.com>\0" + " linuxppc-dev@ozlabs.org\0" "\00:1\0" "b\0" "\n" @@ -38,4 +38,4 @@ "\n" --Mika -18ceda0b08cbf21fe199695e00e7f7130658f36e73306d49a3a973c6ab5d03c2 +851c371b327f0d48b47d96723dc52810934e14f38e6b94dc2bec90af400f3255
diff --git a/a/1.txt b/N2/1.txt index 430345a..ac3e814 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,4 +1,3 @@ - > > Right, it's all very clear now. At some point in the future, I'd like > to visit why SPARSEMEM-based hot-add is not always used but it's a @@ -15,3 +14,9 @@ areas and areas beyond e820-end-of-ram. So all the areas are already reserved, until freed. --Mika + +-- +To unsubscribe, send a message with 'unsubscribe linux-mm' in +the body to majordomo@kvack.org. For more info on Linux MM, +see: http://www.linux-mm.org/ . +Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a> diff --git a/a/content_digest b/N2/content_digest index 362bd20..4110bd6 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -10,17 +10,16 @@ "Subject\0Re: [PATCH 4/6] Have x86_64 use add_active_range() and free_area_init_nodes\0" "Date\0Fri, 01 Sep 2006 11:46:46 +0300\0" "To\0Mel Gorman <mel@csn.ul.ie>\0" - "Cc\0akpm@osdl.org" + "Cc\0Keith Mannthey <kmannth@gmail.com>" + akpm@osdl.org tony.luck@intel.com - linuxppc-dev@ozlabs.org + Linux Memory Management List <linux-mm@kvack.org> ak@suse.de bob.picco@hp.com Linux Kernel Mailing List <linux-kernel@vger.kernel.org> - Linux Memory Management List <linux-mm@kvack.org> - " Keith Mannthey <kmannth@gmail.com>\0" + " linuxppc-dev@ozlabs.org\0" "\00:1\0" "b\0" - "\n" ">\n" "> Right, it's all very clear now. At some point in the future, I'd like \n" "> to visit why SPARSEMEM-based hot-add is not always used but it's a \n" @@ -36,6 +35,12 @@ "areas and areas beyond e820-end-of-ram. So all the areas are already \n" "reserved, until freed.\n" "\n" - --Mika + "--Mika\n" + "\n" + "--\n" + "To unsubscribe, send a message with 'unsubscribe linux-mm' in\n" + "the body to majordomo@kvack.org. For more info on Linux MM,\n" + "see: http://www.linux-mm.org/ .\n" + "Don't email: <a href=mailto:\"dont@kvack.org\"> email@kvack.org </a>" -18ceda0b08cbf21fe199695e00e7f7130658f36e73306d49a3a973c6ab5d03c2 +712825d793ba9457e1e34c909702acac43cdb1bde9be4d0db5e0266b1bf2d373
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.