diff for duplicates of <20171124142948.GA1966@samekh> diff --git a/a/1.txt b/N1/1.txt index 20ec5ed..b267b89 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -21,14 +21,14 @@ node might not feasible without changes. One idea could be to add a new property to memory nodes, to specify what memory is potentially hotplugguable. For example, something like: -memory at 0 { +memory@0 { device_type = "memory"; reg = <0x0 0x0 0x0 0x40000000>; hot-add-range = <0x0 0x40000000 0x0 0x40000000>; numa-node-id=<0>; } -memory at 10000000000 { +memory@10000000000 { device_type = "memory"; reg = <0x100 0x0 0x0 0x40000000>; hot-add-range = <0x100 0x40000000 0x0 0x40000000>; @@ -149,4 +149,10 @@ Andrea > > . > > > -> +> + +-- +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/N1/content_digest index de1c2ee..752707f 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,10 +3,22 @@ "ref\05A17F5DF.2040108@huawei.com\0" "ref\020171124104401.GD18120@samekh\0" "ref\05A180DF1.8060009@huawei.com\0" - "From\0ar@linux.vnet.ibm.com (Andrea Reale)\0" - "Subject\0[PATCH v2 4/5] mm: memory_hotplug: Add memory hotremove probe device\0" + "From\0Andrea Reale <ar@linux.vnet.ibm.com>\0" + "Subject\0Re: [PATCH v2 4/5] mm: memory_hotplug: Add memory hotremove probe device\0" "Date\0Fri, 24 Nov 2017 14:29:48 +0000\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0zhong jiang <zhongjiang@huawei.com>\0" + "Cc\0linux-arm-kernel@lists.infradead.org" + linux-kernel@vger.kernel.org + linux-mm@kvack.org + m.bielski@virtualopensystems.com + arunks@qti.qualcomm.com + mark.rutland@arm.com + scott.branden@broadcom.com + will.deacon@arm.com + qiuxishi@huawei.com + catalin.marinas@arm.com + mhocko@suse.com + " realean2@ie.ibm.com\0" "\00:1\0" "b\0" "Hi zhongjian,\n" @@ -32,14 +44,14 @@ "One idea could be to add a new property to memory nodes, to specify what\n" "memory is potentially hotplugguable. For example, something like:\n" "\n" - "memory at 0 {\n" + "memory@0 {\n" " device_type = \"memory\";\n" " reg = <0x0 0x0 0x0 0x40000000>;\n" " hot-add-range = <0x0 0x40000000 0x0 0x40000000>;\n" " numa-node-id=<0>;\n" "}\n" "\n" - "memory at 10000000000 {\n" + "memory@10000000000 {\n" " device_type = \"memory\";\n" " reg = <0x100 0x0 0x0 0x40000000>;\n" " hot-add-range = <0x100 0x40000000 0x0 0x40000000>;\n" @@ -160,6 +172,12 @@ "> > .\n" "> >\n" "> \n" - > + "> \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>" -3a40087735196113269c9602b8fec78ec112707d8e0d81cfd3b9cdd9ecd3b8ac +966166804b25540cd2fd8aa4f909078a6e0124b7f307dc9982da4ba7bc6b3569
diff --git a/a/1.txt b/N2/1.txt index 20ec5ed..ddc6c87 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -21,14 +21,14 @@ node might not feasible without changes. One idea could be to add a new property to memory nodes, to specify what memory is potentially hotplugguable. For example, something like: -memory at 0 { +memory@0 { device_type = "memory"; reg = <0x0 0x0 0x0 0x40000000>; hot-add-range = <0x0 0x40000000 0x0 0x40000000>; numa-node-id=<0>; } -memory at 10000000000 { +memory@10000000000 { device_type = "memory"; reg = <0x100 0x0 0x0 0x40000000>; hot-add-range = <0x100 0x40000000 0x0 0x40000000>; diff --git a/a/content_digest b/N2/content_digest index de1c2ee..5a3bb54 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -3,10 +3,22 @@ "ref\05A17F5DF.2040108@huawei.com\0" "ref\020171124104401.GD18120@samekh\0" "ref\05A180DF1.8060009@huawei.com\0" - "From\0ar@linux.vnet.ibm.com (Andrea Reale)\0" - "Subject\0[PATCH v2 4/5] mm: memory_hotplug: Add memory hotremove probe device\0" + "From\0Andrea Reale <ar@linux.vnet.ibm.com>\0" + "Subject\0Re: [PATCH v2 4/5] mm: memory_hotplug: Add memory hotremove probe device\0" "Date\0Fri, 24 Nov 2017 14:29:48 +0000\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0zhong jiang <zhongjiang@huawei.com>\0" + "Cc\0linux-arm-kernel@lists.infradead.org" + linux-kernel@vger.kernel.org + linux-mm@kvack.org + m.bielski@virtualopensystems.com + arunks@qti.qualcomm.com + mark.rutland@arm.com + scott.branden@broadcom.com + will.deacon@arm.com + qiuxishi@huawei.com + catalin.marinas@arm.com + mhocko@suse.com + " realean2@ie.ibm.com\0" "\00:1\0" "b\0" "Hi zhongjian,\n" @@ -32,14 +44,14 @@ "One idea could be to add a new property to memory nodes, to specify what\n" "memory is potentially hotplugguable. For example, something like:\n" "\n" - "memory at 0 {\n" + "memory@0 {\n" " device_type = \"memory\";\n" " reg = <0x0 0x0 0x0 0x40000000>;\n" " hot-add-range = <0x0 0x40000000 0x0 0x40000000>;\n" " numa-node-id=<0>;\n" "}\n" "\n" - "memory at 10000000000 {\n" + "memory@10000000000 {\n" " device_type = \"memory\";\n" " reg = <0x100 0x0 0x0 0x40000000>;\n" " hot-add-range = <0x100 0x40000000 0x0 0x40000000>;\n" @@ -162,4 +174,4 @@ "> \n" > -3a40087735196113269c9602b8fec78ec112707d8e0d81cfd3b9cdd9ecd3b8ac +793d49123442bfa7f0541340d8c718ef3f152956473c06678523dd8091b20a40
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.