diff for duplicates of <20160630174854.GA23578@lst.de>

diff --git a/a/1.txt b/N1/1.txt
index e4cad15..92023fb 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,4 +1,4 @@
-On Sat, Jun 25, 2016 at 10:05:19PM +0200, Alexander Gordeev wrote:
+On Sat, Jun 25, 2016@10:05:19PM +0200, Alexander Gordeev wrote:
 > > + * and generate an output cpumask suitable for spreading MSI/MSI-X vectors
 > > + * so that they are distributed as good as possible around the CPUs.  If
 > > + * more vectors than CPUs are available we'll map one to each CPU,
@@ -57,8 +57,3 @@ think it's optimal, but I really want to avoid dragging the discussion
 about the optimal algorithm into this patchset.  We should at least
 move to a vector per node/socket model instead of just the siblings,
 and be able to use all vectors (at least optionally).
-
-_______________________________________________
-Linux-nvme mailing list
-Linux-nvme@lists.infradead.org
-http://lists.infradead.org/mailman/listinfo/linux-nvme
diff --git a/a/content_digest b/N1/content_digest
index 66b831d..bab3282 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,19 +1,12 @@
  "ref\01465934346-20648-1-git-send-email-hch@lst.de\0"
  "ref\01465934346-20648-7-git-send-email-hch@lst.de\0"
  "ref\020160625200518.GA29251@dhcp-27-118.brq.redhat.com\0"
- "From\0Christoph Hellwig <hch@lst.de>\0"
- "Subject\0Re: [PATCH 06/13] irq: add a helper spread an affinity mask for MSI/MSI-X vectors\0"
+ "From\0hch@lst.de (Christoph Hellwig)\0"
+ "Subject\0[PATCH 06/13] irq: add a helper spread an affinity mask for MSI/MSI-X vectors\0"
  "Date\0Thu, 30 Jun 2016 19:48:54 +0200\0"
- "To\0Alexander Gordeev <agordeev@redhat.com>\0"
- "Cc\0linux-block@vger.kernel.org"
-  linux-pci@vger.kernel.org
-  linux-kernel@vger.kernel.org
-  linux-nvme@lists.infradead.org
-  axboe@fb.com
- " tglx@linutronix.de\0"
  "\00:1\0"
  "b\0"
- "On Sat, Jun 25, 2016 at 10:05:19PM +0200, Alexander Gordeev wrote:\n"
+ "On Sat, Jun 25, 2016@10:05:19PM +0200, Alexander Gordeev wrote:\n"
  "> > + * and generate an output cpumask suitable for spreading MSI/MSI-X vectors\n"
  "> > + * so that they are distributed as good as possible around the CPUs.  If\n"
  "> > + * more vectors than CPUs are available we'll map one to each CPU,\n"
@@ -71,11 +64,6 @@
  "think it's optimal, but I really want to avoid dragging the discussion\n"
  "about the optimal algorithm into this patchset.  We should at least\n"
  "move to a vector per node/socket model instead of just the siblings,\n"
- "and be able to use all vectors (at least optionally).\n"
- "\n"
- "_______________________________________________\n"
- "Linux-nvme mailing list\n"
- "Linux-nvme@lists.infradead.org\n"
- http://lists.infradead.org/mailman/listinfo/linux-nvme
+ and be able to use all vectors (at least optionally).
 
-f145aedb7ae587b0e31b743b8c9935c44129eab061bc03202751ea42ffbf4bb6
+88d30965238fcf44d27ba1a6e038debea284bd515453b51f18ba8cd368afab08
