diff for duplicates of <20180604231508.GA10666@linux.intel.com>

diff --git a/a/1.txt b/N1/1.txt
index 11b1662..eeb761e 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,6 +1,6 @@
 On Fri, Jun 01, 2018 at 05:55:13PM -0400, Mike Snitzer wrote:
 > On Tue, May 29 2018 at  3:51pm -0400,
-> Ross Zwisler <ross.zwisler-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> wrote:
+> Ross Zwisler <ross.zwisler@linux.intel.com> wrote:
 > 
 > > Currently the code in dm_dax_direct_access() only checks whether the target
 > > type has a direct_access() operation defined, not whether the underlying
@@ -105,3 +105,7 @@ I'll look into that for the next revision, thanks.
 Right, the goal is to make QUEUE_FLAG_DAX our one source of truth for whether
 DM devices support DAX, and not have it half defined by that and half by the
 DM_TYPE_DAX_BIO_BASED.
+_______________________________________________
+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 d2e2eb9..72380d9 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,21 +1,20 @@
  "ref\020180529195106.14268-1-ross.zwisler@linux.intel.com\0"
  "ref\020180529195106.14268-5-ross.zwisler@linux.intel.com\0"
  "ref\020180601215513.GA18712@redhat.com\0"
- "ref\020180601215513.GA18712-H+wXaHxf7aLQT0dZR+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 4/7] dm: prevent DAX mounts if not supported\0"
  "Date\0Mon, 4 Jun 2018 17:15:08 -0600\0"
- "To\0Mike Snitzer <snitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>\0"
- "Cc\0linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org"
-  linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-  linux-xfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-  dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
- " linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\0"
+ "To\0Mike Snitzer <snitzer@redhat.com>\0"
+ "Cc\0linux-nvdimm@lists.01.org"
+  linux-kernel@vger.kernel.org
+  linux-xfs@vger.kernel.org
+  dm-devel@redhat.com
+ " linux-fsdevel@vger.kernel.org\0"
  "\00:1\0"
  "b\0"
  "On Fri, Jun 01, 2018 at 05:55:13PM -0400, Mike Snitzer wrote:\n"
  "> On Tue, May 29 2018 at  3:51pm -0400,\n"
- "> Ross Zwisler <ross.zwisler-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> wrote:\n"
+ "> Ross Zwisler <ross.zwisler@linux.intel.com> wrote:\n"
  "> \n"
  "> > Currently the code in dm_dax_direct_access() only checks whether the target\n"
  "> > type has a direct_access() operation defined, not whether the underlying\n"
@@ -119,6 +118,10 @@
  "\n"
  "Right, the goal is to make QUEUE_FLAG_DAX our one source of truth for whether\n"
  "DM devices support DAX, and not have it half defined by that and half by the\n"
- DM_TYPE_DAX_BIO_BASED.
+ "DM_TYPE_DAX_BIO_BASED.\n"
+ "_______________________________________________\n"
+ "Linux-nvdimm mailing list\n"
+ "Linux-nvdimm@lists.01.org\n"
+ https://lists.01.org/mailman/listinfo/linux-nvdimm
 
-047ccc62086afe40a038038f73df2f275632c5cfaa161fe9d192024c89d6e197
+207cbae0d8f2cc69ab360a5005f819ac7c24e8f5f68321943ccd9f4e6d2ebddb
