diff for duplicates of <Y3UHOg7E0iRFpjml@google.com> diff --git a/a/1.txt b/N1/1.txt index 0e4b953..30fb74f 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -60,7 +60,3 @@ break KVM). > patch? Hmm, yeah. That'd also be a good place to document why kvm_lock isn't used. -_______________________________________________ -kvmarm mailing list -kvmarm@lists.cs.columbia.edu -https://lists.cs.columbia.edu/mailman/listinfo/kvmarm diff --git a/a/content_digest b/N1/content_digest index f6890c0..a73f111 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -6,40 +6,45 @@ "Date\0Wed, 16 Nov 2022 15:52:26 +0000\0" "To\0Huang" " Kai <kai.huang@intel.com>\0" - "Cc\0mjrosato@linux.ibm.com <mjrosato@linux.ibm.com>" - david@redhat.com <david@redhat.com> - Yao - Yuan <yuan.yao@intel.com> - linux-mips@vger.kernel.org <linux-mips@vger.kernel.org> - linux-riscv@lists.infradead.org <linux-riscv@lists.infradead.org> - imbrenda@linux.ibm.com <imbrenda@linux.ibm.com> - kvmarm@lists.cs.columbia.edu <kvmarm@lists.cs.columbia.edu> - linux-s390@vger.kernel.org <linux-s390@vger.kernel.org> - frankja@linux.ibm.com <frankja@linux.ibm.com> - mpe@ellerman.id.au <mpe@ellerman.id.au> + "Cc\0imbrenda@linux.ibm.com <imbrenda@linux.ibm.com>" + aou@eecs.berkeley.edu <aou@eecs.berkeley.edu> + mjrosato@linux.ibm.com <mjrosato@linux.ibm.com> + vkuznets@redhat.com <vkuznets@redhat.com> + farman@linux.ibm.com <farman@linux.ibm.com> chenhuacai@kernel.org <chenhuacai@kernel.org> - aleksandar.qemu.devel@gmail.com <aleksandar.qemu.devel@gmail.com> + paul.walmsley@sifive.com <paul.walmsley@sifive.com> + palmer@dabbelt.com <palmer@dabbelt.com> + maz@kernel.org <maz@kernel.org> + anup@brainfault.org <anup@brainfault.org> + pbonzini@redhat.com <pbonzini@redhat.com> borntraeger@linux.ibm.com <borntraeger@linux.ibm.com> - Gao - Chao <chao.gao@intel.com> - farman@linux.ibm.com <farman@linux.ibm.com> - aou@eecs.berkeley.edu <aou@eecs.berkeley.edu> + aleksandar.qemu.devel@gmail.com <aleksandar.qemu.devel@gmail.com> + frankja@linux.ibm.com <frankja@linux.ibm.com> + oliver.upton@linux.dev <oliver.upton@linux.dev> kvm@vger.kernel.org <kvm@vger.kernel.org> - paul.walmsley@sifive.com <paul.walmsley@sifive.com> - kvmarm@lists.linux.dev <kvmarm@lists.linux.dev> + Yao + Yuan <yuan.yao@intel.com> + farosas@linux.ibm.com <farosas@linux.ibm.com> + david@redhat.com <david@redhat.com> + james.morse@arm.com <james.morse@arm.com> + mpe@ellerman.id.au <mpe@ellerman.id.au> + alexandru.elisei@arm.com <alexandru.elisei@arm.com> + linux-s390@vger.kernel.org <linux-s390@vger.kernel.org> + linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org> tglx@linutronix.de <tglx@linutronix.de> - linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org> Yamahata Isaku <isaku.yamahata@intel.com> - atishp@atishpatra.org <atishp@atishpatra.org> - farosas@linux.ibm.com <farosas@linux.ibm.com> - linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org> - palmer@dabbelt.com <palmer@dabbelt.com> + kvmarm@lists.linux.dev <kvmarm@lists.linux.dev> + suzuki.poulose@arm.com <suzuki.poulose@arm.com> kvm-riscv@lists.infradead.org <kvm-riscv@lists.infradead.org> - maz@kernel.org <maz@kernel.org> - pbonzini@redhat.com <pbonzini@redhat.com> - vkuznets@redhat.com <vkuznets@redhat.com> - " linuxppc-dev@lists.ozlabs.org <linuxppc-dev@lists.ozlabs.org>\0" + linuxppc-dev@lists.ozlabs.org <linuxppc-dev@lists.ozlabs.org> + linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org> + linux-mips@vger.kernel.org <linux-mips@vger.kernel.org> + kvmarm@lists.cs.columbia.edu <kvmarm@lists.cs.columbia.edu> + Gao + Chao <chao.gao@intel.com> + atishp@atishpatra.org <atishp@atishpatra.org> + " linux-riscv@lists.infradead.org <linux-riscv@lists.infradead.org>\0" "\00:1\0" "b\0" "On Wed, Nov 16, 2022, Huang, Kai wrote:\n" @@ -103,10 +108,6 @@ "> Also, do you also want to update Documentation/virt/kvm/locking.rst\" in this\n" "> patch?\n" "\n" - "Hmm, yeah. That'd also be a good place to document why kvm_lock isn't used.\n" - "_______________________________________________\n" - "kvmarm mailing list\n" - "kvmarm@lists.cs.columbia.edu\n" - https://lists.cs.columbia.edu/mailman/listinfo/kvmarm + Hmm, yeah. That'd also be a good place to document why kvm_lock isn't used. -8fc194fc019684311f1b713d77abb56797f447b34dccf88082bc6121e8dbfb10 +b3b86c908afd71fd6e55496d82164f9bf70544bf32aebd1cdcdcc128d89f8914
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox