diff for duplicates of <20170823163826.GB25999@linux.intel.com>

diff --git a/a/1.txt b/N1/1.txt
index 3216690..41d2af0 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,5 +1,5 @@
-On Tue, Aug 22, 2017 at 08:37:04PM -0700, rdodgen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:
-> From: Randy Dodgen <dodgen-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
+On Tue, Aug 22, 2017 at 08:37:04PM -0700, rdodgen@gmail.com wrote:
+> From: Randy Dodgen <dodgen@google.com>
 > 
 > If an ext4 filesystem is mounted with both the DAX and read-only
 > options, executables on that filesystem will fail to start (claiming
@@ -19,7 +19,7 @@ On Tue, Aug 22, 2017 at 08:37:04PM -0700, rdodgen-Re5JQEeQqe8AvxtiuMwx3w@public.
 > dax_iomap_fault). These is some overlap already (e.g. grabbing journal
 > handles).
 > 
-> Signed-off-by: Randy Dodgen <dodgen-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
+> Signed-off-by: Randy Dodgen <dodgen@google.com>
 > ---
 > 
 > I'm resending for some DMARC-proofing (thanks Ted for the explanation), a
@@ -86,3 +86,7 @@ non-DAX case, but I don't see any more checks for VM_SHARED or
 FAULT_FLAG_WRITE in fs/ext4, so maybe there is a better way?
 
 - Ross
+_______________________________________________
+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 42cd575..ff0a58e 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,18 +1,17 @@
  "ref\020170822222434.146233-1-dodgen@google.com\0"
  "ref\0bea6897723e5bf09d893b2ca40263a894a284a5a.1503459187.git.dodgen@google.com\0"
- "ref\0bea6897723e5bf09d893b2ca40263a894a284a5a.1503459187.git.dodgen-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org\0"
- "From\0Ross Zwisler <ross.zwisler-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>\0"
+ "From\0Ross Zwisler <ross.zwisler@linux.intel.com>\0"
  "Subject\0Re: [PATCH v2] Fix ext4 fault handling when mounted with -o dax,ro\0"
  "Date\0Wed, 23 Aug 2017 10:38:26 -0600\0"
- "To\0rdodgen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org\0"
- "Cc\0linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
-  tytso-3s7WtUTddSA@public.gmane.org
-  Randy Dodgen <dodgen-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
- " linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org\0"
+ "To\0rdodgen@gmail.com\0"
+ "Cc\0linux-ext4@vger.kernel.org"
+  tytso@mit.edu
+  Randy Dodgen <dodgen@google.com>
+ " linux-nvdimm@lists.01.org\0"
  "\00:1\0"
  "b\0"
- "On Tue, Aug 22, 2017 at 08:37:04PM -0700, rdodgen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:\n"
- "> From: Randy Dodgen <dodgen-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>\n"
+ "On Tue, Aug 22, 2017 at 08:37:04PM -0700, rdodgen@gmail.com wrote:\n"
+ "> From: Randy Dodgen <dodgen@google.com>\n"
  "> \n"
  "> If an ext4 filesystem is mounted with both the DAX and read-only\n"
  "> options, executables on that filesystem will fail to start (claiming\n"
@@ -32,7 +31,7 @@
  "> dax_iomap_fault). These is some overlap already (e.g. grabbing journal\n"
  "> handles).\n"
  "> \n"
- "> Signed-off-by: Randy Dodgen <dodgen-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>\n"
+ "> Signed-off-by: Randy Dodgen <dodgen@google.com>\n"
  "> ---\n"
  "> \n"
  "> I'm resending for some DMARC-proofing (thanks Ted for the explanation), a\n"
@@ -98,6 +97,10 @@
  "non-DAX case, but I don't see any more checks for VM_SHARED or\n"
  "FAULT_FLAG_WRITE in fs/ext4, so maybe there is a better way?\n"
  "\n"
- - Ross
+ "- Ross\n"
+ "_______________________________________________\n"
+ "Linux-nvdimm mailing list\n"
+ "Linux-nvdimm@lists.01.org\n"
+ https://lists.01.org/mailman/listinfo/linux-nvdimm
 
-2cc2ce2eba1da5ab5b48afdde17cc0825b54d518abf08ddded392924b0d4b170
+4b63576dcbb1f9a0581c1b2d5f0bee0284c74d391081dc4ebb88f289ff4213c5
