All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20170817145411.GE2566@flask>

diff --git a/a/content_digest b/N1/content_digest
index 2124bd2..edbc299 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -2,7 +2,7 @@
  "ref\0b77b151f-e51d-3657-66e9-6fbc83887b18@suse.de\0"
  "From\0Radim Kr\304\215m\303\241\305\231 <rkrcmar@redhat.com>\0"
  "Subject\0Re: [PATCH RFC 0/2] KVM: use RCU to allow dynamic kvm->vcpus array\0"
- "Date\0Thu, 17 Aug 2017 14:54:12 +0000\0"
+ "Date\0Thu, 17 Aug 2017 16:54:12 +0200\0"
  "To\0Alexander Graf <agraf@suse.de>\0"
  "Cc\0linux-mips@linux-mips.org"
   linux-arm-kernel@lists.infradead.org
@@ -78,4 +78,4 @@
  "Yeah, I skipped the growing as it was not necessary for the\n"
  illustration.
 
-f5f62cdd4ea72a7e71169ba235f6bf415320ea740c598a4efab5f8339ccf06d7
+968e84572ecd0ccc7b8099e6e5b1ac855baf84325887d636dcaaa24e076deae1

diff --git a/a/1.txt b/N2/1.txt
index 06b7d49..3d07e85 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -1,5 +1,5 @@
 2017-08-17 09:04+0200, Alexander Graf:
-> On 16.08.17 21:40, Radim Krčmář  wrote:
+> On 16.08.17 21:40, Radim Kr?m??  wrote:
 > > The goal is to increase KVM_MAX_VCPUS without worrying about memory
 > > impact of many small guests.
 > > 
@@ -13,7 +13,7 @@
 > > start.  The main advantage is that kvm->vcpus will work like it does
 > > now.  It has been posted as "[PATCH 0/4] KVM: add KVM_CREATE_VM2 to
 > > allow dynamic kvm->vcpus array",
-> > http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1377285.html
+> > http://www.mail-archive.com/linux-kernel at vger.kernel.org/msg1377285.html
 > > 
 > > The main problem of (2), this series, is that we cannot extend the array
 > > in place and therefore require some kind of protection when moving it.
diff --git a/a/content_digest b/N2/content_digest
index 2124bd2..d4f0dcc 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -1,27 +1,13 @@
  "ref\020170816194037.9460-1-rkrcmar@redhat.com\0"
  "ref\0b77b151f-e51d-3657-66e9-6fbc83887b18@suse.de\0"
- "From\0Radim Kr\304\215m\303\241\305\231 <rkrcmar@redhat.com>\0"
- "Subject\0Re: [PATCH RFC 0/2] KVM: use RCU to allow dynamic kvm->vcpus array\0"
- "Date\0Thu, 17 Aug 2017 14:54:12 +0000\0"
- "To\0Alexander Graf <agraf@suse.de>\0"
- "Cc\0linux-mips@linux-mips.org"
-  linux-arm-kernel@lists.infradead.org
-  kvm@vger.kernel.org
-  kvm-ppc@vger.kernel.org
-  linux-kernel@vger.kernel.org
-  linux-s390@vger.kernel.org
-  Marc Zyngier <marc.zyngier@arm.com>
-  Christian Borntraeger <borntraeger@de.ibm.com>
-  James Hogan <james.hogan@imgtec.com>
-  Christoffer Dall <cdall@linaro.org>
-  Paul Mackerras <paulus@ozlabs.org>
-  Cornelia Huck <cohuck@redhat.com>
-  David Hildenbrand <david@redhat.com>
- " Paolo Bonzini <pbonzini@redhat.com>\0"
+ "From\0rkrcmar@redhat.com (Radim Kr\304\215m\303\241\305\231)\0"
+ "Subject\0[PATCH RFC 0/2] KVM: use RCU to allow dynamic kvm->vcpus array\0"
+ "Date\0Thu, 17 Aug 2017 16:54:12 +0200\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "2017-08-17 09:04+0200, Alexander Graf:\n"
- "> On 16.08.17 21:40, Radim Kr\304\215m\303\241\305\231  wrote:\n"
+ "> On 16.08.17 21:40, Radim Kr?m??  wrote:\n"
  "> > The goal is to increase KVM_MAX_VCPUS without worrying about memory\n"
  "> > impact of many small guests.\n"
  "> > \n"
@@ -35,7 +21,7 @@
  "> > start.  The main advantage is that kvm->vcpus will work like it does\n"
  "> > now.  It has been posted as \"[PATCH 0/4] KVM: add KVM_CREATE_VM2 to\n"
  "> > allow dynamic kvm->vcpus array\",\n"
- "> > http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1377285.html\n"
+ "> > http://www.mail-archive.com/linux-kernel at vger.kernel.org/msg1377285.html\n"
  "> > \n"
  "> > The main problem of (2), this series, is that we cannot extend the array\n"
  "> > in place and therefore require some kind of protection when moving it.\n"
@@ -78,4 +64,4 @@
  "Yeah, I skipped the growing as it was not necessary for the\n"
  illustration.
 
-f5f62cdd4ea72a7e71169ba235f6bf415320ea740c598a4efab5f8339ccf06d7
+ad1bea7e3e321c4ff84133783fd13787be399f986fca4e0a6acf64de93ff10de

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.