diff for duplicates of <20180525125126.GA9275@redhat.com>

diff --git a/a/1.txt b/N1/1.txt
index e8dae4a..44c28a3 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,11 +1,11 @@
 On Fri, May 25 2018 at  2:17am -0400,
-Mikulas Patocka <mpatocka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
+Mikulas Patocka <mpatocka@redhat.com> wrote:
 
 > 
 > 
 > On Thu, 24 May 2018, Dan Williams wrote:
 > 
-> > On Fri, May 18, 2018 at 10:25 PM, Mikulas Patocka <mpatocka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
+> > On Fri, May 18, 2018 at 10:25 PM, Mikulas Patocka <mpatocka@redhat.com> wrote:
 > > > Use new API for flushing persistent memory.
 > > >
 > > > The problem is this:
@@ -107,5 +107,9 @@ and CONFIG_ARCH_HAS_UACCESS_FLUSHCACHE and they absolutely don't take
 into account the duality of the different programming models needed to
 achieve optimal cross-architecture use of persistent memory).
 
-Signed-off-by: Mikulas Patocka <mpatocka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
-Signed-off-by: Mike Snitzer <msnitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
+Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
+Signed-off-by: Mike Snitzer <msnitzer@redhat.com>
+_______________________________________________
+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 6a5bd7b..9c8fc44 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -2,24 +2,23 @@
  "ref\020180519052635.567438191@debian.vm\0"
  "ref\0CAPcyv4iEtfuVGPR0QMKcafv2XFwSj3nzxjX8cuXpXe00akAvYA@mail.gmail.com\0"
  "ref\0alpine.LRH.2.02.1805250213270.13894@file01.intranet.prod.int.rdu2.redhat.com\0"
- "ref\0alpine.LRH.2.02.1805250213270.13894-Hpncn10jQN4oNljnaZt3ZvA+iT7yCHsGwRM8/txMwJMAicBL8TP8PQ@public.gmane.org\0"
- "From\0Mike Snitzer <snitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>\0"
+ "From\0Mike Snitzer <snitzer@redhat.com>\0"
  "Subject\0Re: [patch 4/4] dm-writecache: use new API for flushing\0"
  "Date\0Fri, 25 May 2018 08:51:26 -0400\0"
- "To\0Dan Williams <dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>\0"
- "Cc\0device-mapper development <dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>"
-  Mikulas Patocka <mpatocka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
- " linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org\0"
+ "To\0Dan Williams <dan.j.williams@intel.com>\0"
+ "Cc\0device-mapper development <dm-devel@redhat.com>"
+  Mikulas Patocka <mpatocka@redhat.com>
+ " linux-nvdimm@lists.01.org\0"
  "\00:1\0"
  "b\0"
  "On Fri, May 25 2018 at  2:17am -0400,\n"
- "Mikulas Patocka <mpatocka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:\n"
+ "Mikulas Patocka <mpatocka@redhat.com> wrote:\n"
  "\n"
  "> \n"
  "> \n"
  "> On Thu, 24 May 2018, Dan Williams wrote:\n"
  "> \n"
- "> > On Fri, May 18, 2018 at 10:25 PM, Mikulas Patocka <mpatocka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:\n"
+ "> > On Fri, May 18, 2018 at 10:25 PM, Mikulas Patocka <mpatocka@redhat.com> wrote:\n"
  "> > > Use new API for flushing persistent memory.\n"
  "> > >\n"
  "> > > The problem is this:\n"
@@ -121,7 +120,11 @@
  "into account the duality of the different programming models needed to\n"
  "achieve optimal cross-architecture use of persistent memory).\n"
  "\n"
- "Signed-off-by: Mikulas Patocka <mpatocka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>\n"
- Signed-off-by: Mike Snitzer <msnitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
+ "Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>\n"
+ "Signed-off-by: Mike Snitzer <msnitzer@redhat.com>\n"
+ "_______________________________________________\n"
+ "Linux-nvdimm mailing list\n"
+ "Linux-nvdimm@lists.01.org\n"
+ https://lists.01.org/mailman/listinfo/linux-nvdimm
 
-9030507adbb79f0b0e7f6b8a17943fcbb4c92dfed9b2b9859b76a2fd19ffe6fe
+ccdceba44367fc5ae9b77e0deb775ad0d7b09fc39af2d80623044c716daab3a9
