diff for duplicates of <281b12de-7730-05a7-1187-e4f702c19cda@gmail.com>

diff --git a/a/1.txt b/N1/1.txt
index e8a7797..284de7c 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -17,8 +17,3 @@ split, a kernel stack managed socket, and dedicated H/W queues for the
 socket and those are all common to what the nvme patches are doing. So,
 can we create a common framework for those characteristics which enables
 other use cases (like a more generic Rx zerocopy)?
-
-_______________________________________________
-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 9d10ef8..e4453bc 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -12,26 +12,26 @@
  "Subject\0Re: [PATCH v1 net-next 02/15] net: Introduce direct data placement tcp offload\0"
  "Date\0Fri, 11 Dec 2020 12:59:52 -0700\0"
  "To\0Jakub Kicinski <kuba@kernel.org>\0"
- "Cc\0Yoray Zack <yorayz@mellanox.com>"
-  sagi@grimberg.me
-  yorayz@nvidia.com
-  Boris Pismenny <borisp@nvidia.com>
-  boris.pismenny@gmail.com
-  Ben Ben-Ishay <benishay@mellanox.com>
-  edumazet@google.com
-  linux-nvme@lists.infradead.org
+ "Cc\0Boris Pismenny <borispismenny@gmail.com>"
+  Boris Pismenny <borisp@mellanox.com>
   davem@davemloft.net
+  saeedm@nvidia.com
+  hch@lst.de
+  sagi@grimberg.me
   axboe@fb.com
-  Boris Pismenny <borispismenny@gmail.com>
-  ogerlitz@nvidia.com
+  kbusch@kernel.org
   viro@zeniv.linux.org.uk
+  edumazet@google.com
+  boris.pismenny@gmail.com
+  linux-nvme@lists.infradead.org
   netdev@vger.kernel.org
-  kbusch@kernel.org
-  Or Gerlitz <ogerlitz@mellanox.com>
   benishay@nvidia.com
-  saeedm@nvidia.com
-  hch@lst.de
- " Boris Pismenny <borisp@mellanox.com>\0"
+  ogerlitz@nvidia.com
+  yorayz@nvidia.com
+  Ben Ben-Ishay <benishay@mellanox.com>
+  Or Gerlitz <ogerlitz@mellanox.com>
+  Yoray Zack <yorayz@mellanox.com>
+ " Boris Pismenny <borisp@nvidia.com>\0"
  "\00:1\0"
  "b\0"
  "On 12/11/20 11:45 AM, Jakub Kicinski wrote:\n"
@@ -52,11 +52,6 @@
  "split, a kernel stack managed socket, and dedicated H/W queues for the\n"
  "socket and those are all common to what the nvme patches are doing. So,\n"
  "can we create a common framework for those characteristics which enables\n"
- "other use cases (like a more generic Rx zerocopy)?\n"
- "\n"
- "_______________________________________________\n"
- "Linux-nvme mailing list\n"
- "Linux-nvme@lists.infradead.org\n"
- http://lists.infradead.org/mailman/listinfo/linux-nvme
+ other use cases (like a more generic Rx zerocopy)?
 
-4b928dd355204c1133a4bf4dab5a9468c63b2a12e743345b6ce65465349025f0
+c62d2257bbe97c4e2a47f1b2505974c0e0dcb3cd1dc0ff74da00a8f3f444f8a4
