diff for duplicates of <20160330123922.GA11351@dhcppc0.redhat.com>

diff --git a/a/1.txt b/N1/1.txt
index ed9f15d..cf41572 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -41,11 +41,11 @@ On 30/03/2016:09:46:38 AM, Dave Young wrote:
 > >     on the memory consumption of the kdump system. In general this is not
 > >     dependent on the memory size of the production system.
 > >  
-> > -   On arm, use "crashkernel=Y@X". Note that the start address of the kernel
+> > -   On arm, use "crashkernel=Y at X". Note that the start address of the kernel
 > > -   will be aligned to 128MiB (0x08000000), so if the start address is not then
 > > -   any space below the alignment point may be overwritten by the dump-capture kernel,
 > > -   which means it is possible that the vmcore is not that precise as expected.
-> > +   On arm, the use of "crashkernel=Y@X" is no longer necessary; the
+> > +   On arm, the use of "crashkernel=Y at X" is no longer necessary; the
 > > +   kernel will automatically locate the crash kernel image within the
 > > +   first 512MB of RAM if X is not given.
 > >  
@@ -74,8 +74,3 @@ region is memory and not reserved, then allow to reserve. That might help to
 remove 512M restriction.
 
 ~Pratyush
-
-_______________________________________________
-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 315b7d7..66853ca 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,16 +1,9 @@
  "ref\0E1akqb5-0002LZ-1f@rmk-PC.arm.linux.org.uk\0"
  "ref\020160330014638.GA6993@dhcp-128-65.nay.redhat.com\0"
- "From\0Pratyush Anand <panand@redhat.com>\0"
- "Subject\0Re: [PATCH] ARM: kexec: fix crashkernel= handling\0"
+ "From\0panand@redhat.com (Pratyush Anand)\0"
+ "Subject\0[PATCH] ARM: kexec: fix crashkernel= handling\0"
  "Date\0Wed, 30 Mar 2016 18:09:22 +0530\0"
- "To\0Dave Young <dyoung@redhat.com>"
- " Russell King <rmk+kernel@arm.linux.org.uk>\0"
- "Cc\0linux-doc@vger.kernel.org"
-  Jonathan Corbet <corbet@lwn.net>
-  kexec@lists.infradead.org
-  Haren Myneni <hbabu@us.ibm.com>
-  Vivek Goyal <vgoyal@redhat.com>
- " linux-arm-kernel@lists.infradead.org\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "On 30/03/2016:09:46:38 AM, Dave Young wrote:\n"
@@ -56,11 +49,11 @@
  "> >     on the memory consumption of the kdump system. In general this is not\n"
  "> >     dependent on the memory size of the production system.\n"
  "> >  \n"
- "> > -   On arm, use \"crashkernel=Y@X\". Note that the start address of the kernel\n"
+ "> > -   On arm, use \"crashkernel=Y at X\". Note that the start address of the kernel\n"
  "> > -   will be aligned to 128MiB (0x08000000), so if the start address is not then\n"
  "> > -   any space below the alignment point may be overwritten by the dump-capture kernel,\n"
  "> > -   which means it is possible that the vmcore is not that precise as expected.\n"
- "> > +   On arm, the use of \"crashkernel=Y@X\" is no longer necessary; the\n"
+ "> > +   On arm, the use of \"crashkernel=Y at X\" is no longer necessary; the\n"
  "> > +   kernel will automatically locate the crash kernel image within the\n"
  "> > +   first 512MB of RAM if X is not given.\n"
  "> >  \n"
@@ -88,11 +81,6 @@
  "region is memory and not reserved, then allow to reserve. That might help to\n"
  "remove 512M restriction.\n"
  "\n"
- "~Pratyush\n"
- "\n"
- "_______________________________________________\n"
- "kexec mailing list\n"
- "kexec@lists.infradead.org\n"
- http://lists.infradead.org/mailman/listinfo/kexec
+ ~Pratyush
 
-54a5d9d068afb64e4f709bcc77692fcb52aefdb6f976e2731ac5c8e05dddb576
+90dea7e4683f79d295dbac01aaf814d47334258b5c829a79670499a16a801ed7
