All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <ZnmRgqD6FmXNNzzI@google.com>

diff --git a/a/1.txt b/N1/1.txt
index 78176df..e80ac79 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -19,7 +19,7 @@ Yep!
 > As mentioned above, some of the patches in this series(especially 1-4 & 6) that
 > does the VFIO cleanups and dropping CONFIG_KVM_VFIO looks very straightforward
 > and useful. I am thinking of including those when I re-spin my RFC series, if
-> that?s ok.
+> that’s ok.
 
 Please don't include them, as the patch they build towards (patch 5) is buggy[*],
 and I am fairly certain that at least some of the patches will change significantly.
@@ -27,8 +27,8 @@ and I am fairly certain that at least some of the patches will change significan
 I expect to re-start working on the series in ~2 weeks, and am planning on actively
 pushing the series (i.e. not ignoring it for months on end).
 
-[*] https://lore.kernel.org/all/ZWp_q1w01NCZi8KX at google.com
+[*] https://lore.kernel.org/all/ZWp_q1w01NCZi8KX@google.com
 
 > Please let me know your thoughts.
 >
-> [1]. https://lore.kernel.org/linux-iommu/20240209115824.GA2922446 at myrica
+> [1]. https://lore.kernel.org/linux-iommu/20240209115824.GA2922446@myrica
diff --git a/a/content_digest b/N1/content_digest
index ca55684..e0f715c 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,9 +1,52 @@
  "ref\020230916003118.2540661-1-seanjc@google.com\0"
  "ref\0504fa0a7264d4762afda2f13c3525ce5@huawei.com\0"
  "From\0Sean Christopherson <seanjc@google.com>\0"
- "Subject\0[PATCH 00/26] KVM: vfio: Hide KVM internals from others\0"
+ "Subject\0Re: [PATCH 00/26] KVM: vfio: Hide KVM internals from others\0"
  "Date\0Mon, 24 Jun 2024 08:32:18 -0700\0"
- "To\0kvm-riscv@lists.infradead.org\0"
+ "To\0Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>\0"
+ "Cc\0Catalin Marinas <catalin.marinas@arm.com>"
+  Will Deacon <will@kernel.org>
+  Marc Zyngier <maz@kernel.org>
+  Oliver Upton <oliver.upton@linux.dev>
+  Huacai Chen <chenhuacai@kernel.org>
+  Michael Ellerman <mpe@ellerman.id.au>
+  Anup Patel <anup@brainfault.org>
+  Paul Walmsley <paul.walmsley@sifive.com>
+  Palmer Dabbelt <palmer@dabbelt.com>
+  Albert Ou <aou@eecs.berkeley.edu>
+  Heiko Carstens <hca@linux.ibm.com>
+  Vasily Gorbik <gor@linux.ibm.com>
+  Alexander Gordeev <agordeev@linux.ibm.com>
+  Christian Borntraeger <borntraeger@linux.ibm.com>
+  Janosch Frank <frankja@linux.ibm.com>
+  Claudio Imbrenda <imbrenda@linux.ibm.com>
+  Thomas Gleixner <tglx@linutronix.de>
+  Ingo Molnar <mingo@redhat.com>
+  Borislav Petkov <bp@alien8.de>
+  Dave Hansen <dave.hansen@linux.intel.com>
+  x86@kernel.org <x86@kernel.org>
+  Peter Zijlstra <peterz@infradead.org>
+  Arnaldo Carvalho de Melo <acme@kernel.org>
+  Paolo Bonzini <pbonzini@redhat.com>
+  Tony Krowiak <akrowiak@linux.ibm.com>
+  Halil Pasic <pasic@linux.ibm.com>
+  Jason Herne <jjherne@linux.ibm.com>
+  Harald Freudenberger <freude@linux.ibm.com>
+  Alex Williamson <alex.williamson@redhat.com>
+  Andy Lutomirski <luto@kernel.org>
+  linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>
+  kvmarm@lists.linux.dev <kvmarm@lists.linux.dev>
+  linux-mips@vger.kernel.org <linux-mips@vger.kernel.org>
+  kvm@vger.kernel.org <kvm@vger.kernel.org>
+  linuxppc-dev@lists.ozlabs.org <linuxppc-dev@lists.ozlabs.org>
+  kvm-riscv@lists.infradead.org <kvm-riscv@lists.infradead.org>
+  linux-riscv@lists.infradead.org <linux-riscv@lists.infradead.org>
+  linux-s390@vger.kernel.org <linux-s390@vger.kernel.org>
+  linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>
+  linux-perf-users@vger.kernel.org <linux-perf-users@vger.kernel.org>
+  Anish Ghulati <aghulati@google.com>
+  Venkatesh Srinivas <venkateshs@chromium.org>
+ " Andrew Thornton <andrewth@google.com>\0"
  "\00:1\0"
  "b\0"
  "On Thu, Jun 20, 2024, Shameerali Kolothum Thodi wrote:\n"
@@ -27,7 +70,7 @@
  "> As mentioned above, some of the patches in this series(especially 1-4 & 6) that\n"
  "> does the VFIO cleanups and dropping CONFIG_KVM_VFIO looks very straightforward\n"
  "> and useful. I am thinking of including those when I re-spin my RFC series, if\n"
- "> that?s ok.\n"
+ "> that\342\200\231s ok.\n"
  "\n"
  "Please don't include them, as the patch they build towards (patch 5) is buggy[*],\n"
  "and I am fairly certain that at least some of the patches will change significantly.\n"
@@ -35,10 +78,10 @@
  "I expect to re-start working on the series in ~2 weeks, and am planning on actively\n"
  "pushing the series (i.e. not ignoring it for months on end).\n"
  "\n"
- "[*] https://lore.kernel.org/all/ZWp_q1w01NCZi8KX at google.com\n"
+ "[*] https://lore.kernel.org/all/ZWp_q1w01NCZi8KX@google.com\n"
  "\n"
  "> Please let me know your thoughts.\n"
  ">\n"
- > [1]. https://lore.kernel.org/linux-iommu/20240209115824.GA2922446 at myrica
+ > [1]. https://lore.kernel.org/linux-iommu/20240209115824.GA2922446@myrica
 
-1d3f961e7ede408ea70745a594fbcdb722910e3d6884971d32258e610528d6c1
+ebd71bab937e17b408cad296f1191d80cf07cca270f8f141cbb63b44a261984b

diff --git a/a/1.txt b/N2/1.txt
index 78176df..462e1ab 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -19,7 +19,7 @@ Yep!
 > As mentioned above, some of the patches in this series(especially 1-4 & 6) that
 > does the VFIO cleanups and dropping CONFIG_KVM_VFIO looks very straightforward
 > and useful. I am thinking of including those when I re-spin my RFC series, if
-> that?s ok.
+> that’s ok.
 
 Please don't include them, as the patch they build towards (patch 5) is buggy[*],
 and I am fairly certain that at least some of the patches will change significantly.
@@ -27,8 +27,13 @@ and I am fairly certain that at least some of the patches will change significan
 I expect to re-start working on the series in ~2 weeks, and am planning on actively
 pushing the series (i.e. not ignoring it for months on end).
 
-[*] https://lore.kernel.org/all/ZWp_q1w01NCZi8KX at google.com
+[*] https://lore.kernel.org/all/ZWp_q1w01NCZi8KX@google.com
 
 > Please let me know your thoughts.
 >
-> [1]. https://lore.kernel.org/linux-iommu/20240209115824.GA2922446 at myrica
+> [1]. https://lore.kernel.org/linux-iommu/20240209115824.GA2922446@myrica 
+
+_______________________________________________
+linux-riscv mailing list
+linux-riscv@lists.infradead.org
+http://lists.infradead.org/mailman/listinfo/linux-riscv
diff --git a/a/content_digest b/N2/content_digest
index ca55684..ba0db16 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -1,9 +1,52 @@
  "ref\020230916003118.2540661-1-seanjc@google.com\0"
  "ref\0504fa0a7264d4762afda2f13c3525ce5@huawei.com\0"
  "From\0Sean Christopherson <seanjc@google.com>\0"
- "Subject\0[PATCH 00/26] KVM: vfio: Hide KVM internals from others\0"
+ "Subject\0Re: [PATCH 00/26] KVM: vfio: Hide KVM internals from others\0"
  "Date\0Mon, 24 Jun 2024 08:32:18 -0700\0"
- "To\0kvm-riscv@lists.infradead.org\0"
+ "To\0Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>\0"
+ "Cc\0Catalin Marinas <catalin.marinas@arm.com>"
+  Will Deacon <will@kernel.org>
+  Marc Zyngier <maz@kernel.org>
+  Oliver Upton <oliver.upton@linux.dev>
+  Huacai Chen <chenhuacai@kernel.org>
+  Michael Ellerman <mpe@ellerman.id.au>
+  Anup Patel <anup@brainfault.org>
+  Paul Walmsley <paul.walmsley@sifive.com>
+  Palmer Dabbelt <palmer@dabbelt.com>
+  Albert Ou <aou@eecs.berkeley.edu>
+  Heiko Carstens <hca@linux.ibm.com>
+  Vasily Gorbik <gor@linux.ibm.com>
+  Alexander Gordeev <agordeev@linux.ibm.com>
+  Christian Borntraeger <borntraeger@linux.ibm.com>
+  Janosch Frank <frankja@linux.ibm.com>
+  Claudio Imbrenda <imbrenda@linux.ibm.com>
+  Thomas Gleixner <tglx@linutronix.de>
+  Ingo Molnar <mingo@redhat.com>
+  Borislav Petkov <bp@alien8.de>
+  Dave Hansen <dave.hansen@linux.intel.com>
+  x86@kernel.org <x86@kernel.org>
+  Peter Zijlstra <peterz@infradead.org>
+  Arnaldo Carvalho de Melo <acme@kernel.org>
+  Paolo Bonzini <pbonzini@redhat.com>
+  Tony Krowiak <akrowiak@linux.ibm.com>
+  Halil Pasic <pasic@linux.ibm.com>
+  Jason Herne <jjherne@linux.ibm.com>
+  Harald Freudenberger <freude@linux.ibm.com>
+  Alex Williamson <alex.williamson@redhat.com>
+  Andy Lutomirski <luto@kernel.org>
+  linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>
+  kvmarm@lists.linux.dev <kvmarm@lists.linux.dev>
+  linux-mips@vger.kernel.org <linux-mips@vger.kernel.org>
+  kvm@vger.kernel.org <kvm@vger.kernel.org>
+  linuxppc-dev@lists.ozlabs.org <linuxppc-dev@lists.ozlabs.org>
+  kvm-riscv@lists.infradead.org <kvm-riscv@lists.infradead.org>
+  linux-riscv@lists.infradead.org <linux-riscv@lists.infradead.org>
+  linux-s390@vger.kernel.org <linux-s390@vger.kernel.org>
+  linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>
+  linux-perf-users@vger.kernel.org <linux-perf-users@vger.kernel.org>
+  Anish Ghulati <aghulati@google.com>
+  Venkatesh Srinivas <venkateshs@chromium.org>
+ " Andrew Thornton <andrewth@google.com>\0"
  "\00:1\0"
  "b\0"
  "On Thu, Jun 20, 2024, Shameerali Kolothum Thodi wrote:\n"
@@ -27,7 +70,7 @@
  "> As mentioned above, some of the patches in this series(especially 1-4 & 6) that\n"
  "> does the VFIO cleanups and dropping CONFIG_KVM_VFIO looks very straightforward\n"
  "> and useful. I am thinking of including those when I re-spin my RFC series, if\n"
- "> that?s ok.\n"
+ "> that\342\200\231s ok.\n"
  "\n"
  "Please don't include them, as the patch they build towards (patch 5) is buggy[*],\n"
  "and I am fairly certain that at least some of the patches will change significantly.\n"
@@ -35,10 +78,15 @@
  "I expect to re-start working on the series in ~2 weeks, and am planning on actively\n"
  "pushing the series (i.e. not ignoring it for months on end).\n"
  "\n"
- "[*] https://lore.kernel.org/all/ZWp_q1w01NCZi8KX at google.com\n"
+ "[*] https://lore.kernel.org/all/ZWp_q1w01NCZi8KX@google.com\n"
  "\n"
  "> Please let me know your thoughts.\n"
  ">\n"
- > [1]. https://lore.kernel.org/linux-iommu/20240209115824.GA2922446 at myrica
+ "> [1]. https://lore.kernel.org/linux-iommu/20240209115824.GA2922446@myrica \n"
+ "\n"
+ "_______________________________________________\n"
+ "linux-riscv mailing list\n"
+ "linux-riscv@lists.infradead.org\n"
+ http://lists.infradead.org/mailman/listinfo/linux-riscv
 
-1d3f961e7ede408ea70745a594fbcdb722910e3d6884971d32258e610528d6c1
+dcc33446c2e6cf49e33c2cbfdf7c1465817a77a1adf436d78b8e9260979179a9

diff --git a/a/1.txt b/N3/1.txt
index 78176df..e80ac79 100644
--- a/a/1.txt
+++ b/N3/1.txt
@@ -19,7 +19,7 @@ Yep!
 > As mentioned above, some of the patches in this series(especially 1-4 & 6) that
 > does the VFIO cleanups and dropping CONFIG_KVM_VFIO looks very straightforward
 > and useful. I am thinking of including those when I re-spin my RFC series, if
-> that?s ok.
+> that’s ok.
 
 Please don't include them, as the patch they build towards (patch 5) is buggy[*],
 and I am fairly certain that at least some of the patches will change significantly.
@@ -27,8 +27,8 @@ and I am fairly certain that at least some of the patches will change significan
 I expect to re-start working on the series in ~2 weeks, and am planning on actively
 pushing the series (i.e. not ignoring it for months on end).
 
-[*] https://lore.kernel.org/all/ZWp_q1w01NCZi8KX at google.com
+[*] https://lore.kernel.org/all/ZWp_q1w01NCZi8KX@google.com
 
 > Please let me know your thoughts.
 >
-> [1]. https://lore.kernel.org/linux-iommu/20240209115824.GA2922446 at myrica
+> [1]. https://lore.kernel.org/linux-iommu/20240209115824.GA2922446@myrica
diff --git a/a/content_digest b/N3/content_digest
index ca55684..400f39d 100644
--- a/a/content_digest
+++ b/N3/content_digest
@@ -1,9 +1,51 @@
  "ref\020230916003118.2540661-1-seanjc@google.com\0"
  "ref\0504fa0a7264d4762afda2f13c3525ce5@huawei.com\0"
  "From\0Sean Christopherson <seanjc@google.com>\0"
- "Subject\0[PATCH 00/26] KVM: vfio: Hide KVM internals from others\0"
+ "Subject\0Re: [PATCH 00/26] KVM: vfio: Hide KVM internals from others\0"
  "Date\0Mon, 24 Jun 2024 08:32:18 -0700\0"
- "To\0kvm-riscv@lists.infradead.org\0"
+ "To\0Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>\0"
+ "Cc\0x86@kernel.org <x86@kernel.org>"
+  kvm@vger.kernel.org <kvm@vger.kernel.org>
+  Peter Zijlstra <peterz@infradead.org>
+  Catalin Marinas <catalin.marinas@arm.com>
+  Dave Hansen <dave.hansen@linux.intel.com>
+  linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>
+  Alexander Gordeev <agordeev@linux.ibm.com>
+  Claudio Imbrenda <imbrenda@linux.ibm.com>
+  Will Deacon <will@kernel.org>
+  linux-riscv@lists.infradead.org <linux-riscv@lists.infradead.org>
+  linux-s390@vger.kernel.org <linux-s390@vger.kernel.org>
+  Janosch Frank <frankja@linux.ibm.com>
+  Harald Freudenberger <freude@linux.ibm.com>
+  Marc Zyngier <maz@kernel.org>
+  Huacai Chen <chenhuacai@kernel.org>
+  Halil Pasic <pasic@linux.ibm.com>
+  Andrew Thornton <andrewth@google.com>
+  Ingo Molnar <mingo@redhat.com>
+  Christian Borntraeger <borntraeger@linux.ibm.com>
+  Jason Herne <jjherne@linux.ibm.com>
+  Albert Ou <aou@eecs.berkeley.edu>
+  Vasily Gorbik <gor@linux.ibm.com>
+  Venkatesh Srinivas <venkateshs@chromium.org>
+  Heiko Carstens <hca@linux.ibm.com>
+  Arnaldo Carvalho de Melo <acme@kernel.org>
+  Alex Williamson <alex.williamson@redhat.com>
+  Borislav Petkov <bp@alien8.de>
+  Andy Lutomirski <luto@kernel.org>
+  Paul Walmsley <paul.walmsley@sifive.com>
+  kvmarm@lists.linux.dev <kvmarm@lists.linux.dev>
+  Thomas Gleixner <tglx@linutronix.de>
+  linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>
+  Tony Krowiak <akrowiak@linux.ibm.com>
+  Anish Ghulati <aghulati@google.com>
+  linux-mips@vger.kernel.org <linux-mips@vger.kernel.org>
+  Oliver Upton <oliver.upton@linux.dev>
+  linux-perf-users@vger.kernel.org <linux-perf-users@vger.kernel.org>
+  Palmer Dabbelt <palmer@dabbelt.com>
+  kvm-riscv@lists.infradead.org <kvm-riscv@lists.infradead.org>
+  Anup Patel <anup@brainfault.org>
+  Paolo Bonzini <pbonzini@redhat.com>
+ " linuxppc-dev@lists.ozlabs.org <linuxppc-dev@lists.ozlabs.org>\0"
  "\00:1\0"
  "b\0"
  "On Thu, Jun 20, 2024, Shameerali Kolothum Thodi wrote:\n"
@@ -27,7 +69,7 @@
  "> As mentioned above, some of the patches in this series(especially 1-4 & 6) that\n"
  "> does the VFIO cleanups and dropping CONFIG_KVM_VFIO looks very straightforward\n"
  "> and useful. I am thinking of including those when I re-spin my RFC series, if\n"
- "> that?s ok.\n"
+ "> that\342\200\231s ok.\n"
  "\n"
  "Please don't include them, as the patch they build towards (patch 5) is buggy[*],\n"
  "and I am fairly certain that at least some of the patches will change significantly.\n"
@@ -35,10 +77,10 @@
  "I expect to re-start working on the series in ~2 weeks, and am planning on actively\n"
  "pushing the series (i.e. not ignoring it for months on end).\n"
  "\n"
- "[*] https://lore.kernel.org/all/ZWp_q1w01NCZi8KX at google.com\n"
+ "[*] https://lore.kernel.org/all/ZWp_q1w01NCZi8KX@google.com\n"
  "\n"
  "> Please let me know your thoughts.\n"
  ">\n"
- > [1]. https://lore.kernel.org/linux-iommu/20240209115824.GA2922446 at myrica
+ > [1]. https://lore.kernel.org/linux-iommu/20240209115824.GA2922446@myrica
 
-1d3f961e7ede408ea70745a594fbcdb722910e3d6884971d32258e610528d6c1
+5a7f41026aa914955541e6cfca5e75ed1310f5f784a9830be569139decbe3eea

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.