diff for duplicates of <20200414092201.GD4247@MiWiFi-R3L-srv> diff --git a/a/1.txt b/N1/1.txt index 29fb4b6..8b71bbe 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -156,9 +156,3 @@ know the details. So in this case, is there any flag or a way to know those memory block are hotpluggable? I am curious how those kernel data is avoided to be put in this area. Or ppc just freely uses it for kernel data or user space data, then try to migrate when hot remove? - - -_______________________________________________ -kexec mailing list -kexec@lists.infradead.org -http://lists.infradead.org/mailman/listinfo/kexec diff --git a/a/content_digest b/N1/content_digest index cac3269..3ba4d1e 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -183,12 +183,6 @@ "know the details. So in this case, is there any flag or a way to know\n" "those memory block are hotpluggable? I am curious how those kernel data\n" "is avoided to be put in this area. Or ppc just freely uses it for kernel\n" - "data or user space data, then try to migrate when hot remove?\n" - "\n" - "\n" - "_______________________________________________\n" - "kexec mailing list\n" - "kexec@lists.infradead.org\n" - http://lists.infradead.org/mailman/listinfo/kexec + data or user space data, then try to migrate when hot remove? -eb958d57bbc5d2265e273e80ca7803800694dc86a9272ddbe6dc37b2d2c2821a +bf7a05edf713f2c0ef09e6c33a69fc37bca9c188d0241ab1ec6e4b0790b8b2f8
diff --git a/a/1.txt b/N2/1.txt index 29fb4b6..860cb75 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -159,6 +159,6 @@ data or user space data, then try to migrate when hot remove? _______________________________________________ -kexec mailing list -kexec@lists.infradead.org -http://lists.infradead.org/mailman/listinfo/kexec +linux-arm-kernel mailing list +linux-arm-kernel@lists.infradead.org +http://lists.infradead.org/mailman/listinfo/linux-arm-kernel diff --git a/a/content_digest b/N2/content_digest index cac3269..e77e4ea 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -187,8 +187,8 @@ "\n" "\n" "_______________________________________________\n" - "kexec mailing list\n" - "kexec@lists.infradead.org\n" - http://lists.infradead.org/mailman/listinfo/kexec + "linux-arm-kernel mailing list\n" + "linux-arm-kernel@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -eb958d57bbc5d2265e273e80ca7803800694dc86a9272ddbe6dc37b2d2c2821a +abf6342dc43df84e7742c3a2be017b24c46da0beced4f70661b83873ca2098c1
diff --git a/a/1.txt b/N3/1.txt index 29fb4b6..8b71bbe 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -156,9 +156,3 @@ know the details. So in this case, is there any flag or a way to know those memory block are hotpluggable? I am curious how those kernel data is avoided to be put in this area. Or ppc just freely uses it for kernel data or user space data, then try to migrate when hot remove? - - -_______________________________________________ -kexec mailing list -kexec@lists.infradead.org -http://lists.infradead.org/mailman/listinfo/kexec diff --git a/a/content_digest b/N3/content_digest index cac3269..e87aaa2 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -12,18 +12,18 @@ "Subject\0Re: [PATCH 1/3] kexec: Prevent removal of memory in use by a loaded kexec image\0" "Date\0Tue, 14 Apr 2020 17:22:01 +0800\0" "To\0David Hildenbrand <david@redhat.com>\0" - "Cc\0Anshuman Khandual <anshuman.khandual@arm.com>" + "Cc\0Eric W. Biederman <ebiederm@xmission.com>" + Russell King - ARM Linux admin <linux@armlinux.org.uk> + Anshuman Khandual <anshuman.khandual@arm.com> Catalin Marinas <catalin.marinas@arm.com> Bhupesh Sharma <bhsharma@redhat.com> - linuxppc-dev@lists.ozlabs.org kexec@lists.infradead.org - Russell King - ARM Linux admin <linux@armlinux.org.uk> linux-mm@kvack.org James Morse <james.morse@arm.com> - Eric W. Biederman <ebiederm@xmission.com> Andrew Morton <akpm@linux-foundation.org> Will Deacon <will@kernel.org> - " linux-arm-kernel@lists.infradead.org\0" + linux-arm-kernel@lists.infradead.org + " linuxppc-dev@lists.ozlabs.org\0" "\00:1\0" "b\0" "On 04/14/20 at 10:00am, David Hildenbrand wrote:\n" @@ -183,12 +183,6 @@ "know the details. So in this case, is there any flag or a way to know\n" "those memory block are hotpluggable? I am curious how those kernel data\n" "is avoided to be put in this area. Or ppc just freely uses it for kernel\n" - "data or user space data, then try to migrate when hot remove?\n" - "\n" - "\n" - "_______________________________________________\n" - "kexec mailing list\n" - "kexec@lists.infradead.org\n" - http://lists.infradead.org/mailman/listinfo/kexec + data or user space data, then try to migrate when hot remove? -eb958d57bbc5d2265e273e80ca7803800694dc86a9272ddbe6dc37b2d2c2821a +6bb21a40d6de6afd32fa1abe483423cf7c9b5b224de4bba1bfb9cb8b3bcd6e3b
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.