diff for duplicates of <20170725205416.GC20979@redhat.com>

diff --git a/a/1.txt b/N1/1.txt
index 5ddf916..8ff1c39 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,6 +1,6 @@
 On Tue, Jul 25, 2017 at 04:46:09PM -0400, Mike Snitzer wrote:
 > On Tue, Jul 25 2017 at  3:43pm -0400,
-> Vivek Goyal <vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
+> Vivek Goyal <vgoyal@redhat.com> wrote:
 > 
 > > Right now, dm_dax_flush() is not being called and I think it is not being
 > > called becuase DAXDEV_WRITE_CACHE is not set on dm dax device.
@@ -8,7 +8,7 @@ On Tue, Jul 25, 2017 at 04:46:09PM -0400, Mike Snitzer wrote:
 > > If underlying dax device supports write cache, set DAXDEV_WRITE_CACHE on
 > > dm dax device. This will get dm_dax_flush() being called.
 > > 
-> > Signed-off-by: Vivek Goyal <vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
+> > Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
 > 
 > In general this looks mostly OK.. but it seems a bit weird to on the one
 > hand: test if DAXDEV_WRITE_CACHE is set on underlying device.  And on
@@ -20,3 +20,7 @@ On Tue, Jul 25, 2017 at 04:46:09PM -0400, Mike Snitzer wrote:
 Sounds good. I will rename it in next version.
 
 Vivek
+_______________________________________________
+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 f68291e..9070846 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,17 +1,16 @@
  "ref\020170725194337.GA20979@redhat.com\0"
  "ref\020170725204608.GA27693@redhat.com\0"
- "ref\020170725204608.GA27693-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org\0"
- "From\0Vivek Goyal <vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>\0"
+ "From\0Vivek Goyal <vgoyal@redhat.com>\0"
  "Subject\0Re: dm,dax: Make sure dm_dax_flush() is called if device supports it\0"
  "Date\0Tue, 25 Jul 2017 16:54:16 -0400\0"
- "To\0Mike Snitzer <snitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>\0"
- "Cc\0dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
- " linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org\0"
+ "To\0Mike Snitzer <snitzer@redhat.com>\0"
+ "Cc\0dm-devel@redhat.com"
+ " linux-nvdimm@lists.01.org\0"
  "\00:1\0"
  "b\0"
  "On Tue, Jul 25, 2017 at 04:46:09PM -0400, Mike Snitzer wrote:\n"
  "> On Tue, Jul 25 2017 at  3:43pm -0400,\n"
- "> Vivek Goyal <vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:\n"
+ "> Vivek Goyal <vgoyal@redhat.com> wrote:\n"
  "> \n"
  "> > Right now, dm_dax_flush() is not being called and I think it is not being\n"
  "> > called becuase DAXDEV_WRITE_CACHE is not set on dm dax device.\n"
@@ -19,7 +18,7 @@
  "> > If underlying dax device supports write cache, set DAXDEV_WRITE_CACHE on\n"
  "> > dm dax device. This will get dm_dax_flush() being called.\n"
  "> > \n"
- "> > Signed-off-by: Vivek Goyal <vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>\n"
+ "> > Signed-off-by: Vivek Goyal <vgoyal@redhat.com>\n"
  "> \n"
  "> In general this looks mostly OK.. but it seems a bit weird to on the one\n"
  "> hand: test if DAXDEV_WRITE_CACHE is set on underlying device.  And on\n"
@@ -30,6 +29,10 @@
  "\n"
  "Sounds good. I will rename it in next version.\n"
  "\n"
- Vivek
+ "Vivek\n"
+ "_______________________________________________\n"
+ "Linux-nvdimm mailing list\n"
+ "Linux-nvdimm@lists.01.org\n"
+ https://lists.01.org/mailman/listinfo/linux-nvdimm
 
-c7c294a1e1f7ff688f2c96f84ed8216668e6e89d9d9f4ef439e21f9aef37fb59
+186060a4b9626db78b6ae5cb7c20758cf0e438db21fc77c3107b8745cc6ecaa6
