diff for duplicates of <20180612181542.GB28436@linux.intel.com>

diff --git a/a/1.txt b/N1/1.txt
index 9f6b9b7..dd85154 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -93,7 +93,3 @@ that instead of WARN_ON_ONCE() for an empty entry, we'd hit it instead for an
 unlocked entry).
 
 Is that okay?  Or do we need to insert a locked empty entry here?
-_______________________________________________
-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 f9b2863..f4db637 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -4,11 +4,11 @@
  "Subject\0Re: [PATCH v4 10/12] filesystem-dax: Introduce dax_lock_page()\0"
  "Date\0Tue, 12 Jun 2018 12:15:42 -0600\0"
  "To\0Dan Williams <dan.j.williams@intel.com>\0"
- "Cc\0linux-fsdevel@vger.kernel.org"
+ "Cc\0linux-nvdimm@lists.01.org"
+  linux-fsdevel@vger.kernel.org
   linux-mm@kvack.org
   jack@suse.cz
-  hch@lst.de
- " linux-nvdimm@lists.01.org\0"
+ " hch@lst.de\0"
  "\00:1\0"
  "b\0"
  "On Fri, Jun 08, 2018 at 04:51:14PM -0700, Dan Williams wrote:\n"
@@ -105,10 +105,6 @@
  "that instead of WARN_ON_ONCE() for an empty entry, we'd hit it instead for an\n"
  "unlocked entry).\n"
  "\n"
- "Is that okay?  Or do we need to insert a locked empty entry here?\n"
- "_______________________________________________\n"
- "Linux-nvdimm mailing list\n"
- "Linux-nvdimm@lists.01.org\n"
- https://lists.01.org/mailman/listinfo/linux-nvdimm
+ Is that okay?  Or do we need to insert a locked empty entry here?
 
-538ddaf83c0e7c5fb61f62f77d0bb0ad2561807cb11b8a69f5f6759ad2581243
+a714d70ffa17038765a824eba675fb8dc7c03a4af2a420290a2ba923ab400e28
