All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <53C53B77.3080000@samsung.com>

diff --git a/a/1.txt b/N1/1.txt
index 38ca377..acb355f 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -14,7 +14,7 @@ On 07/14/14 19:13, Christoph Lameter wrote:
 > 
 
 Not sure. This sparsemem/vmemmap thing is kinda new to me, so I need to dig some more
-to understand how it iтteracts with kasan.
+to understand how it i?teracts with kasan.
 
 As far as I understand the main problem with sparsemem & kasan is shadow allocation:
 
diff --git a/a/content_digest b/N1/content_digest
index 73b7c3e..a475e0e 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -2,32 +2,10 @@
  "ref\053C08876.10209@zytor.com\0"
  "ref\0CAPAsAGwb2sLmu0o_o-pFP5pXhMs-1sZSJbA3ji=W+JPOZRepgg@mail.gmail.com\0"
  "ref\0alpine.DEB.2.11.1407141012520.25405@gentwo.org\0"
- "From\0Andrey Ryabinin <a.ryabinin@samsung.com>\0"
- "Subject\0Re: [RFC/PATCH -next 00/21] Address sanitizer for kernel (kasan) - dynamic memory error detector.\0"
+ "From\0a.ryabinin@samsung.com (Andrey Ryabinin)\0"
+ "Subject\0[RFC/PATCH -next 00/21] Address sanitizer for kernel (kasan) - dynamic memory error detector.\0"
  "Date\0Tue, 15 Jul 2014 18:32:23 +0400\0"
- "To\0Christoph Lameter <cl@gentwo.org>"
- " Andrey Ryabinin <ryabinin.a.a@gmail.com>\0"
- "Cc\0H. Peter Anvin <hpa@zytor.com>"
-  linux-kernel@vger.kernel.org
-  Dmitry Vyukov <dvyukov@google.com>
-  Konstantin Serebryany <kcc@google.com>
-  Alexey Preobrazhensky <preobr@google.com>
-  Andrey Konovalov <adech.fo@gmail.com>
-  Yuri Gribov <tetra2005@gmail.com>
-  Konstantin Khlebnikov <koct9i@gmail.com>
-  Sasha Levin <sasha.levin@oracle.com>
-  Michal Marek <mmarek@suse.cz>
-  Russell King <linux@arm.linux.org.uk>
-  Thomas Gleixner <tglx@linutronix.de>
-  Ingo Molnar <mingo@redhat.com>
-  Pekka Enberg <penberg@kernel.org>
-  David Rientjes <rientjes@google.com>
-  Joonsoo Kim <iamjoonsoo.kim@lge.com>
-  Andrew Morton <akpm@linux-foundation.org>
-  linux-kbuild@vger.kernel.org
-  linux-arm-kernel@lists.infradead.org
-  x86@kernel.org
- " linux-mm@kvack.org\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "On 07/14/14 19:13, Christoph Lameter wrote:\n"
@@ -46,7 +24,7 @@
  "> \n"
  "\n"
  "Not sure. This sparsemem/vmemmap thing is kinda new to me, so I need to dig some more\n"
- "to understand how it i\321\202teracts with kasan.\n"
+ "to understand how it i?teracts with kasan.\n"
  "\n"
  "As far as I understand the main problem with sparsemem & kasan is shadow allocation:\n"
  "\n"
@@ -57,4 +35,4 @@
  "\n"
  If we don't have one big enough physically contiguous block for shadow it will fail.
 
-2cdfcd1ab3aae8f98715492efa4c78a07dc45fc48cfb4752330a818894f1666c
+5b8253c2adb3f54dbf20f19497f545ebb973ca0a400b6bad886a6c4a28da0f4e

diff --git a/a/1.txt b/N2/1.txt
index 38ca377..e961674 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -14,7 +14,7 @@ On 07/14/14 19:13, Christoph Lameter wrote:
 > 
 
 Not sure. This sparsemem/vmemmap thing is kinda new to me, so I need to dig some more
-to understand how it iтteracts with kasan.
+to understand how it iN?teracts with kasan.
 
 As far as I understand the main problem with sparsemem & kasan is shadow allocation:
 
@@ -24,3 +24,9 @@ As far as I understand the main problem with sparsemem & kasan is shadow allocat
 	shadow_phys_start = memblock_alloc(shadow_size, PAGE_SIZE);
 
 If we don't have one big enough physically contiguous block for shadow it will fail.
+
+--
+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 73b7c3e..a0655a6 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -46,7 +46,7 @@
  "> \n"
  "\n"
  "Not sure. This sparsemem/vmemmap thing is kinda new to me, so I need to dig some more\n"
- "to understand how it i\321\202teracts with kasan.\n"
+ "to understand how it iN?teracts with kasan.\n"
  "\n"
  "As far as I understand the main problem with sparsemem & kasan is shadow allocation:\n"
  "\n"
@@ -55,6 +55,12 @@
  "\n"
  "\tshadow_phys_start = memblock_alloc(shadow_size, PAGE_SIZE);\n"
  "\n"
- If we don't have one big enough physically contiguous block for shadow it will fail.
+ "If we don't have one big enough physically contiguous block for shadow it will fail.\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>"
 
-2cdfcd1ab3aae8f98715492efa4c78a07dc45fc48cfb4752330a818894f1666c
+97c298c7178435328f5711bec3938e72ea0dc9058c925827f21f65d90f1224c9

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.