diff for duplicates of <20180606172421.GA2208@linux.intel.com>

diff --git a/a/1.txt b/N1/1.txt
index 8f24a31..f914d74 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,10 +1,10 @@
 On Mon, Jun 04, 2018 at 08:46:28PM -0400, Mike Snitzer wrote:
 > On Mon, Jun 04 2018 at  7:24pm -0400,
-> Ross Zwisler <ross.zwisler-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> wrote:
+> Ross Zwisler <ross.zwisler@linux.intel.com> wrote:
 > 
 > > On Fri, Jun 01, 2018 at 06:04:43PM -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:
 > > > 
 > > > > The DM_TYPE_DAX_BIO_BASED dm_queue_mode was introduced to prevent DM
 > > > > devices that could possibly support DAX from transitioning into DM devices
@@ -103,3 +103,7 @@ Right?  If so, then I don't see how a transition of the DM device from
 supporting DAX to not supporting DAX or vice versa could harm us, as we can't
 be doing filesystem I/O at the time when we change the composition of the DM
 device.
+_______________________________________________
+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 e8c225c..3229448 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -3,25 +3,24 @@
  "ref\020180601220443.GB18712@redhat.com\0"
  "ref\020180604232416.GB10666@linux.intel.com\0"
  "ref\020180605004558.GB6898@redhat.com\0"
- "ref\020180605004558.GB6898-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 5/7] dm: remove DM_TYPE_DAX_BIO_BASED dm_queue_mode\0"
  "Date\0Wed, 6 Jun 2018 11:24:21 -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 Mon, Jun 04, 2018 at 08:46:28PM -0400, Mike Snitzer wrote:\n"
  "> On Mon, Jun 04 2018 at  7:24pm -0400,\n"
- "> Ross Zwisler <ross.zwisler-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> wrote:\n"
+ "> Ross Zwisler <ross.zwisler@linux.intel.com> wrote:\n"
  "> \n"
  "> > On Fri, Jun 01, 2018 at 06:04:43PM -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"
  "> > > > The DM_TYPE_DAX_BIO_BASED dm_queue_mode was introduced to prevent DM\n"
  "> > > > devices that could possibly support DAX from transitioning into DM devices\n"
@@ -119,6 +118,10 @@
  "Right?  If so, then I don't see how a transition of the DM device from\n"
  "supporting DAX to not supporting DAX or vice versa could harm us, as we can't\n"
  "be doing filesystem I/O at the time when we change the composition of the DM\n"
- device.
+ "device.\n"
+ "_______________________________________________\n"
+ "Linux-nvdimm mailing list\n"
+ "Linux-nvdimm@lists.01.org\n"
+ https://lists.01.org/mailman/listinfo/linux-nvdimm
 
-ff44667c6d683a59d7c65ef1ff33a01d585dec78d2c68ede3588ba52f3d35cf8
+03bbc899aca5ce619a68eb584ef3d92480927fe31ff97e1617b3c9ec1bb76db6
