diff for duplicates of <ZRyn0nPQpbVpz8ah@google.com> diff --git a/a/1.txt b/N1/1.txt index b322662..eb87458 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,5 +1,5 @@ On Tue, Oct 03, 2023, Anish Moorthy wrote: -> On Mon, Oct 2, 2023 at 6:43?PM Sean Christopherson <seanjc@google.com> wrote: +> On Mon, Oct 2, 2023 at 6:43 PM Sean Christopherson <seanjc@google.com> wrote: > > > > > - I should go drop the patches annotating kvm_vcpu_read/write_page > > > from my series @@ -44,7 +44,7 @@ WARNs that are user-triggerable, at least not in upstream. Internally, we can and probably should add a canary, and an aggressive one at that, but I can't think of a sane way to add a canary in upstream while avoiding the known offenders. :-( -> [1] https://lore.kernel.org/all/202309141107.30863e9d-oliver.sang at intel.com +> [1] https://lore.kernel.org/all/202309141107.30863e9d-oliver.sang@intel.com > > > Anyways, don't do anything just yet. > diff --git a/a/content_digest b/N1/content_digest index c451a2b..6ee3a31 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -6,13 +6,40 @@ "ref\0ZRtxoaJdVF1C2Mvy@google.com\0" "ref\0CAF7b7mqyU059YpBBVYjTMNXf9VHSc6tbKrQ8avFXYtP6LWMh8Q@mail.gmail.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[RFC PATCH v12 07/33] KVM: Add KVM_EXIT_MEMORY_FAULT exit to report faults to userspace\0" + "Subject\0Re: [RFC PATCH v12 07/33] KVM: Add KVM_EXIT_MEMORY_FAULT exit to report faults to userspace\0" "Date\0Tue, 3 Oct 2023 16:46:26 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Anish Moorthy <amoorthy@google.com>\0" + "Cc\0Xiaoyao Li <xiaoyao.li@intel.com>" + Paolo Bonzini <pbonzini@redhat.com> + 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> + kvm@vger.kernel.org + kvmarm@lists.linux.dev + kvm-riscv@lists.infradead.org + linux-kernel@vger.kernel.org + Chao Peng <chao.p.peng@linux.intel.com> + Fuad Tabba <tabba@google.com> + Jarkko Sakkinen <jarkko@kernel.org> + Yu Zhang <yu.c.zhang@linux.intel.com> + Isaku Yamahata <isaku.yamahata@intel.com> + Xu Yilun <yilun.xu@intel.com> + Vlastimil Babka <vbabka@suse.cz> + Vishal Annapurve <vannapurve@google.com> + Ackerley Tng <ackerleytng@google.com> + Maciej Szmigiero <mail@maciej.szmigiero.name> + David Hildenbrand <david@redhat.com> + Quentin Perret <qperret@google.com> + Michael Roth <michael.roth@amd.com> + Wang <wei.w.wang@intel.com> + Liam Merwick <liam.merwick@oracle.com> + " Isaku Yamahata <isaku.yamahata@gmail.com>\0" "\00:1\0" "b\0" "On Tue, Oct 03, 2023, Anish Moorthy wrote:\n" - "> On Mon, Oct 2, 2023 at 6:43?PM Sean Christopherson <seanjc@google.com> wrote:\n" + "> On Mon, Oct 2, 2023 at 6:43\342\200\257PM Sean Christopherson <seanjc@google.com> wrote:\n" "> >\n" "> > > - I should go drop the patches annotating kvm_vcpu_read/write_page\n" "> > > from my series\n" @@ -57,7 +84,7 @@ "and probably should add a canary, and an aggressive one at that, but I can't think\n" "of a sane way to add a canary in upstream while avoiding the known offenders. :-(\n" "\n" - "> [1] https://lore.kernel.org/all/202309141107.30863e9d-oliver.sang at intel.com\n" + "> [1] https://lore.kernel.org/all/202309141107.30863e9d-oliver.sang@intel.com\n" "> \n" "> > Anyways, don't do anything just yet.\n" "> \n" @@ -65,4 +92,4 @@ "\n" LOL -d1917fac1db08fd2844180f95dd915e8fb9cfb7659a4583737726f33a6b4699d +cb4e2a37c0fea977279947c171cae98de03ece9155478da85fc47aa7fda98dc5
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.