diff for duplicates of <5B594399.1080404@huawei.com>

diff --git a/a/1.txt b/N1/1.txt
index 84c46ca..fdb48c2 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -86,7 +86,7 @@ Passthrough is not enough to support VFIO, and virtualization need the later.
 > 
 > * I don't want to say "security" here, since I'm actually a lot less concerned about the theoretical malicious endpoint/wild write scenarios than the the much more straightforward malfunctioning device and/or buggy driver causing use-after-free style memory corruption. Also, I'm sick of the word "security"...
 
-OK，We really have no need to consider buggy devices.
+OK?We really have no need to consider buggy devices.
 
 > 
 >>
@@ -114,8 +114,3 @@ OK，We really have no need to consider buggy devices.
 -- 
 Thanks!
 BestRegards
-
-_______________________________________________
-iommu mailing list
-iommu@lists.linux-foundation.org
-https://lists.linuxfoundation.org/mailman/listinfo/iommu
diff --git a/a/content_digest b/N1/content_digest
index 5f6d026..742685f 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,17 +1,9 @@
  "ref\01531376312-2192-1-git-send-email-thunder.leizhen@huawei.com\0"
  "ref\0aace9ec9-a36a-79a8-98eb-bbedd06f11a4@arm.com\0"
- "ref\0aace9ec9-a36a-79a8-98eb-bbedd06f11a4-5wv7dgnIgG8@public.gmane.org\0"
- "From\0Leizhen (ThunderTown) <thunder.leizhen-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>\0"
- "Subject\0Re: [PATCH v3 0/6] add non-strict mode support for arm-smmu-v3\0"
+ "From\0thunder.leizhen@huawei.com (Leizhen (ThunderTown))\0"
+ "Subject\0[PATCH v3 0/6] add non-strict mode support for arm-smmu-v3\0"
  "Date\0Thu, 26 Jul 2018 11:44:25 +0800\0"
- "To\0Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>"
-  Jean-Philippe Brucker <jean-philippe.brucker-5wv7dgnIgG8@public.gmane.org>
-  Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
-  Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
-  linux-arm-kernel <linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
-  iommu <iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
-  linux-kernel <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
- " LinuxArm <linuxarm-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "\n"
@@ -102,7 +94,7 @@
  "> \n"
  "> * I don't want to say \"security\" here, since I'm actually a lot less concerned about the theoretical malicious endpoint/wild write scenarios than the the much more straightforward malfunctioning device and/or buggy driver causing use-after-free style memory corruption. Also, I'm sick of the word \"security\"...\n"
  "\n"
- "OK\357\274\214We really have no need to consider buggy devices.\n"
+ "OK?We really have no need to consider buggy devices.\n"
  "\n"
  "> \n"
  ">>\n"
@@ -129,11 +121,6 @@
  "\n"
  "-- \n"
  "Thanks!\n"
- "BestRegards\n"
- "\n"
- "_______________________________________________\n"
- "iommu mailing list\n"
- "iommu@lists.linux-foundation.org\n"
- https://lists.linuxfoundation.org/mailman/listinfo/iommu
+ BestRegards
 
-1efb460dd3d66a35d54bcb61db30b0771a17e385f904e8f8d12692b178dd3cab
+8bc868dbcaaba942eb54597262bba72151b52bcfa97aa0520dc25546c82e4274
