diff for duplicates of <20170103232206.GD1555@ZenIV.linux.org.uk>

diff --git a/a/1.txt b/N1/1.txt
index c574f7e..ba042ff 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -25,7 +25,3 @@ while 64bit case takes care to align the destination for movnt part,
 
 How much of the above is broken and what do the callers rely upon?  In
 particular, is that sfence the right thing for pmem usecases?
-_______________________________________________
-Linux-nvdimm mailing list
-Linux-nvdimm@lists.01.org
-https://lists.01.org/mailman/listinfo/linux-nvdimm
diff --git a/a/content_digest b/N1/content_digest
index 547db08..89939ea 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -12,17 +12,19 @@
  "Subject\0Re: [RFC] memcpy_nocache() and memcpy_writethrough()\0"
  "Date\0Tue, 3 Jan 2017 23:22:06 +0000\0"
  "To\0Dan Williams <dan.j.williams@intel.com>\0"
- "Cc\0linux-nvdimm@lists.01.org <linux-nvdimm@lists.01.org>"
+ "Cc\0Elliott"
+  Robert (Persistent Memory) <elliott@hpe.com>
+  Boaz Harrosh <boaz@plexistor.com>
+  linux-nvdimm@lists.01.org <linux-nvdimm@ml01.01.org>
   Moreno
   Oliver <oliver.moreno@hpe.com>
-  x86@kernel.org
-  <x86@kernel.org>
+  x86@kernel.org <x86@kernel.org>
   linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>
   Ingo Molnar <mingo@redhat.com>
   H. Peter Anvin <hpa@zytor.com>
   Thomas Gleixner <tglx@linutronix.de>
-  Linus Torvalds <torvalds@linux-foundation.org>
- " boylston@burromesa.net <boylston@burromesa.net>\0"
+  boylston@burromesa.net <boylston@burromesa.net>
+ " Linus Torvalds <torvalds@linux-foundation.org>\0"
  "\00:1\0"
  "b\0"
  "On Tue, Jan 03, 2017 at 01:14:11PM -0800, Dan Williams wrote:\n"
@@ -51,10 +53,6 @@
  "32bit one does not.\n"
  "\n"
  "How much of the above is broken and what do the callers rely upon?  In\n"
- "particular, is that sfence the right thing for pmem usecases?\n"
- "_______________________________________________\n"
- "Linux-nvdimm mailing list\n"
- "Linux-nvdimm@lists.01.org\n"
- https://lists.01.org/mailman/listinfo/linux-nvdimm
+ particular, is that sfence the right thing for pmem usecases?
 
-8e19843c902295cb8fda2a27727f84bedd3e13177b02788c2a333d062601ef2f
+3a53ec7e81e27bdcd72ddfd344d92f897fcb93d6976f76ce4dc96ad29c9665ac
