diff for duplicates of <YmuqifsJltdh7rpv@localhost.localdomain>

diff --git a/a/1.txt b/N1/1.txt
index 757003f..9a0b509 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -50,7 +50,7 @@ On Thu, Jan 27, 2022 at 11:10:34AM +0100, Joerg Roedel wrote:
 > 
 > The previous version of this patch-set can be found here:
 > 
-> 	https://lore.kernel.org/lkml/20210913155603.28383-1-joro at 8bytes.org/
+> 	https://lore.kernel.org/lkml/20210913155603.28383-1-joro@8bytes.org/
 > 
 > Please review.
 > 
@@ -120,40 +120,40 @@ I tried the patch set with 5.17.0-rc1 kernel, and I have a few questions:
    I found it will exit with 0 when I tried to reboot the VM with sev-es enabled.
    However with only sev enabled, the VM can do reboot with no problem:
 
-[root at dell-per7525-03 ~]# virsh start TW-SEV-ES --console
+[root@dell-per7525-03 ~]# virsh start TW-SEV-ES --console
 ....
 Fedora Linux 35 (Server Edition)
 Kernel 5.17.0-rc1 on an x86_64 (ttyS0)
 ....
-[root at fedora ~]# reboot
+[root@fedora ~]# reboot
 .....
 [   48.077682] reboot: Restarting system
 [   48.078109] reboot: machine restart
                        ^^^^^^^^^^^^^^^ guest vm reached restart
-[root at dell-per7525-03 ~]# echo $?
+[root@dell-per7525-03 ~]# echo $?
 0
 ^^^ qemu-kvm exit with 0, no reboot back to normal VM kernel
-[root at dell-per7525-03 ~]#
+[root@dell-per7525-03 ~]#
 
 2) With sev-es enabled and the 2 patch sets applied: A) [PATCH v3 00/10] x86/sev:
 KEXEC/KDUMP support for SEV-ES guests, and B) [PATCH v6 0/7] KVM: SVM: Add initial
 GHCB protocol version 2 support. I can enable kdump and have vmcore generated:
 
-[root at fedora ~]# dmesg|grep -i sev
+[root@fedora ~]# dmesg|grep -i sev
 [    0.030600] SEV: Hypervisor GHCB protocol version support: min=1 max=2
 [    0.030602] SEV: Using GHCB protocol version 2
 [    0.296144] AMD Memory Encryption Features active: SEV SEV-ES
 [    0.450991] SEV: AP jump table Blob successfully set up
-[root at fedora ~]# kdumpctl status
+[root@fedora ~]# kdumpctl status
 kdump: Kdump is operational
 
 However without the 2 patch sets, I can also enable kdump and have vmcore generated:
 
-[root at fedora ~]# dmesg|grep -i sev
+[root@fedora ~]# dmesg|grep -i sev
 [    0.295754] AMD Memory Encryption Features active: SEV SEV-ES
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ patch set A & B 
 	       not applied, so only have this string.
-[root at fedora ~]# echo c > /proc/sysrq-trigger
+[root@fedora ~]# echo c > /proc/sysrq-trigger
 ...
 [    2.759403] kdump[549]: saving vmcore-dmesg.txt to /sysroot/var/crash/127.0.0.1-2022-04-18-05:58:50/
 [    2.804355] kdump[555]: saving vmcore-dmesg.txt complete
@@ -163,7 +163,7 @@ However without the 2 patch sets, I can also enable kdump and have vmcore genera
 [    7.068981] reboot: Restarting system
 [    7.069340] reboot: machine restart
 
-[root at dell-per7525-03 ~]# echo $?
+[root@dell-per7525-03 ~]# echo $?
 0
 ^^^ same exit issue as question 1.
 
@@ -175,5 +175,5 @@ Tao Liu
  
 > _______________________________________________
 > Virtualization mailing list
-> Virtualization at lists.linux-foundation.org
+> Virtualization@lists.linux-foundation.org
 > https://lists.linuxfoundation.org/mailman/listinfo/virtualization
diff --git a/a/content_digest b/N1/content_digest
index 9990818..4754644 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,8 +1,33 @@
  "ref\020220127101044.13803-1-joro@8bytes.org\0"
  "From\0Tao Liu <ltao@redhat.com>\0"
- "Subject\0[PATCH v3 00/10] x86/sev: KEXEC/KDUMP support for SEV-ES guests\0"
+ "Subject\0Re: [PATCH v3 00/10] x86/sev: KEXEC/KDUMP support for SEV-ES guests\0"
  "Date\0Fri, 29 Apr 2022 17:06:17 +0800\0"
- "To\0kexec@lists.infradead.org\0"
+ "To\0Joerg Roedel <joro@8bytes.org>\0"
+ "Cc\0x86@kernel.org"
+  kvm@vger.kernel.org
+  Peter Zijlstra <peterz@infradead.org>
+  Dave Hansen <dave.hansen@linux.intel.com>
+  virtualization@lists.linux-foundation.org
+  Arvind Sankar <nivedita@alum.mit.edu>
+  hpa@zytor.com
+  Jiri Slaby <jslaby@suse.cz>
+  David Rientjes <rientjes@google.com>
+  Masami Hiramatsu <mhiramat@kernel.org>
+  Martin Radev <martin.b.radev@gmail.com>
+  Tom Lendacky <thomas.lendacky@amd.com>
+  Joerg Roedel <jroedel@suse.de>
+  Kees Cook <keescook@chromium.org>
+  Cfir Cohen <cfir@google.com>
+  linux-coco@lists.linux.dev
+  Andy Lutomirski <luto@kernel.org>
+  Dan Williams <dan.j.williams@intel.com>
+  Juergen Gross <jgross@suse.com>
+  Mike Stunes <mstunes@vmware.com>
+  Sean Christopherson <seanjc@google.com>
+  kexec@lists.infradead.org
+  linux-kernel@vger.kernel.org
+  Eric Biederman <ebiederm@xmission.com>
+ " Erdem Aktas <erdemaktas@google.com>\0"
  "\00:1\0"
  "b\0"
  "On Thu, Jan 27, 2022 at 11:10:34AM +0100, Joerg Roedel wrote:\n"
@@ -57,7 +82,7 @@
  "> \n"
  "> The previous version of this patch-set can be found here:\n"
  "> \n"
- "> \thttps://lore.kernel.org/lkml/20210913155603.28383-1-joro at 8bytes.org/\n"
+ "> \thttps://lore.kernel.org/lkml/20210913155603.28383-1-joro@8bytes.org/\n"
  "> \n"
  "> Please review.\n"
  "> \n"
@@ -127,40 +152,40 @@
  "   I found it will exit with 0 when I tried to reboot the VM with sev-es enabled.\n"
  "   However with only sev enabled, the VM can do reboot with no problem:\n"
  "\n"
- "[root at dell-per7525-03 ~]# virsh start TW-SEV-ES --console\n"
+ "[root@dell-per7525-03 ~]# virsh start TW-SEV-ES --console\n"
  "....\n"
  "Fedora Linux 35 (Server Edition)\n"
  "Kernel 5.17.0-rc1 on an x86_64 (ttyS0)\n"
  "....\n"
- "[root at fedora ~]# reboot\n"
+ "[root@fedora ~]# reboot\n"
  ".....\n"
  "[   48.077682] reboot: Restarting system\n"
  "[   48.078109] reboot: machine restart\n"
  "                       ^^^^^^^^^^^^^^^ guest vm reached restart\n"
- "[root at dell-per7525-03 ~]# echo $?\n"
+ "[root@dell-per7525-03 ~]# echo $?\n"
  "0\n"
  "^^^ qemu-kvm exit with 0, no reboot back to normal VM kernel\n"
- "[root at dell-per7525-03 ~]#\n"
+ "[root@dell-per7525-03 ~]#\n"
  "\n"
  "2) With sev-es enabled and the 2 patch sets applied: A) [PATCH v3 00/10] x86/sev:\n"
  "KEXEC/KDUMP support for SEV-ES guests, and B) [PATCH v6 0/7] KVM: SVM: Add initial\n"
  "GHCB protocol version 2 support. I can enable kdump and have vmcore generated:\n"
  "\n"
- "[root at fedora ~]# dmesg|grep -i sev\n"
+ "[root@fedora ~]# dmesg|grep -i sev\n"
  "[    0.030600] SEV: Hypervisor GHCB protocol version support: min=1 max=2\n"
  "[    0.030602] SEV: Using GHCB protocol version 2\n"
  "[    0.296144] AMD Memory Encryption Features active: SEV SEV-ES\n"
  "[    0.450991] SEV: AP jump table Blob successfully set up\n"
- "[root at fedora ~]# kdumpctl status\n"
+ "[root@fedora ~]# kdumpctl status\n"
  "kdump: Kdump is operational\n"
  "\n"
  "However without the 2 patch sets, I can also enable kdump and have vmcore generated:\n"
  "\n"
- "[root at fedora ~]# dmesg|grep -i sev\n"
+ "[root@fedora ~]# dmesg|grep -i sev\n"
  "[    0.295754] AMD Memory Encryption Features active: SEV SEV-ES\n"
  "               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ patch set A & B \n"
  "\t       not applied, so only have this string.\n"
- "[root at fedora ~]# echo c > /proc/sysrq-trigger\n"
+ "[root@fedora ~]# echo c > /proc/sysrq-trigger\n"
  "...\n"
  "[    2.759403] kdump[549]: saving vmcore-dmesg.txt to /sysroot/var/crash/127.0.0.1-2022-04-18-05:58:50/\n"
  "[    2.804355] kdump[555]: saving vmcore-dmesg.txt complete\n"
@@ -170,7 +195,7 @@
  "[    7.068981] reboot: Restarting system\n"
  "[    7.069340] reboot: machine restart\n"
  "\n"
- "[root at dell-per7525-03 ~]# echo $?\n"
+ "[root@dell-per7525-03 ~]# echo $?\n"
  "0\n"
  "^^^ same exit issue as question 1.\n"
  "\n"
@@ -182,7 +207,7 @@
  " \n"
  "> _______________________________________________\n"
  "> Virtualization mailing list\n"
- "> Virtualization at lists.linux-foundation.org\n"
+ "> Virtualization@lists.linux-foundation.org\n"
  > https://lists.linuxfoundation.org/mailman/listinfo/virtualization
 
-4ba823f705d711fa9d16420a5ede056cb7278232752197eee910bfc5d1b412eb
+9c2a77f162a35148b70afb6457d40e321026daef36248401318b48abd6b817d4
