All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20140519160947.GM15130@arm.com>

diff --git a/a/1.txt b/N1/1.txt
index 72bfec7..9b2c9ac 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -10,7 +10,7 @@ On Mon, May 19, 2014 at 02:54:03AM +0100, Wang Nan wrote:
 > For example:
 > 
 >   For a platform with SECTION_SIZE_BITS == 28 (256MiB) and
->   crashkernel=128M@0x28000000 in kernel cmdline, the second
+>   crashkernel=128M at 0x28000000 in kernel cmdline, the second
 >   kernel is loaded at 0x28000000. Kexec puts elfcorehdr at
 >   0x2ff00000, and passes 'elfcorehdr=0x2ff00000 mem=130048K' to
 >   second kernel. When second kernel start, it tries to use
@@ -22,8 +22,3 @@ So isn't the issue here that you're passing an incorrect mem= parameter
 to the crash kernel?
 
 Will
-
-_______________________________________________
-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 997784b..3206114 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,14 +1,8 @@
  "ref\01400464443-34816-1-git-send-email-wangnan0@huawei.com\0"
- "From\0Will Deacon <will.deacon@arm.com>\0"
- "Subject\0Re: [PATCH Resend] ARM: kdump: makes second kernel use strict pfn_valid\0"
+ "From\0will.deacon@arm.com (Will Deacon)\0"
+ "Subject\0[PATCH Resend] ARM: kdump: makes second kernel use strict pfn_valid\0"
  "Date\0Mon, 19 May 2014 17:09:48 +0100\0"
- "To\0Wang Nan <wangnan0@huawei.com>\0"
- "Cc\0linux@arm.linux.org.uk <linux@arm.linux.org.uk>"
-  kexec@lists.infradead.org <kexec@lists.infradead.org>
-  Geng Hui <hui.geng@huawei.com>
-  Simon Horman <horms@verge.net.au>
-  Andrew Morton <akpm@linux-foundation.org>
- " linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "On Mon, May 19, 2014 at 02:54:03AM +0100, Wang Nan wrote:\n"
@@ -23,7 +17,7 @@
  "> For example:\n"
  "> \n"
  ">   For a platform with SECTION_SIZE_BITS == 28 (256MiB) and\n"
- ">   crashkernel=128M@0x28000000 in kernel cmdline, the second\n"
+ ">   crashkernel=128M at 0x28000000 in kernel cmdline, the second\n"
  ">   kernel is loaded at 0x28000000. Kexec puts elfcorehdr at\n"
  ">   0x2ff00000, and passes 'elfcorehdr=0x2ff00000 mem=130048K' to\n"
  ">   second kernel. When second kernel start, it tries to use\n"
@@ -34,11 +28,6 @@
  "So isn't the issue here that you're passing an incorrect mem= parameter\n"
  "to the crash kernel?\n"
  "\n"
- "Will\n"
- "\n"
- "_______________________________________________\n"
- "kexec mailing list\n"
- "kexec@lists.infradead.org\n"
- http://lists.infradead.org/mailman/listinfo/kexec
+ Will
 
-91cd3427b8a81663e6bab033133773f0ea888339aa995e69a95ee0850136a162
+19f72820351fd9ff4d635179210b1306cf3070f2417e45b5ba31435af209c43d

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.