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

diff --git a/a/1.txt b/N1/1.txt
index f679301..7d43f3d 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -34,7 +34,8 @@ ioctls is rollback to a userspace VMM that isn't aware of the per-VM ioctls, but
 doesn't seem too onerous to tell userspace "don't use these unless your entire fleet
 has upgraded", especially since that requirement/advisement is true for the KVM side
 with respect to new registers regardless of how those registers are accessed.
+
 _______________________________________________
-kvmarm mailing list
-kvmarm@lists.cs.columbia.edu
-https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
+linux-arm-kernel mailing list
+linux-arm-kernel@lists.infradead.org
+http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
diff --git a/a/content_digest b/N1/content_digest
index 775f529..367093f 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -12,11 +12,20 @@
  "Subject\0Re: KVM/arm64: Guest ABI changes do not appear rollback-safe\0"
  "Date\0Tue, 8 Feb 2022 16:58:26 +0000\0"
  "To\0Oliver Upton <oupton@google.com>\0"
- "Cc\0kvm@vger.kernel.org"
-  Marc Zyngier <maz@kernel.org>
-  pshier@google.com
+ "Cc\0Marc Zyngier <maz@kernel.org>"
+  Raghavendra Rao Ananta <rananta@google.com>
+  Andrew Jones <drjones@redhat.com>
   kvmarm@lists.cs.columbia.edu
- " linux-arm-kernel@lists.infradead.org\0"
+  pshier@google.com
+  ricarkol@google.com
+  reijiw@google.com
+  jingzhangos@google.com
+  kvm@vger.kernel.org
+  linux-arm-kernel@lists.infradead.org
+  james.morse@arm.com
+  Alexandru.Elisei@arm.com
+  suzuki.poulose@arm.com
+ " Peter Maydell <peter.maydell@linaro.org>\0"
  "\00:1\0"
  "b\0"
  "On Tue, Feb 08, 2022, Oliver Upton wrote:\n"
@@ -55,9 +64,10 @@
  "doesn't seem too onerous to tell userspace \"don't use these unless your entire fleet\n"
  "has upgraded\", especially since that requirement/advisement is true for the KVM side\n"
  "with respect to new registers regardless of how those registers are accessed.\n"
+ "\n"
  "_______________________________________________\n"
- "kvmarm mailing list\n"
- "kvmarm@lists.cs.columbia.edu\n"
- https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
+ "linux-arm-kernel mailing list\n"
+ "linux-arm-kernel@lists.infradead.org\n"
+ http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
 
-c6420d9e9568c0964ebf4e6503f7fea945ecbb18f14661e2a1f2cdb119bfdd0f
+251128aaff0551fc8d2c86c74eade4391f1b29f58a33e09086ec79c6f676530b

diff --git a/a/1.txt b/N2/1.txt
index f679301..3b496d6 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -34,7 +34,3 @@ ioctls is rollback to a userspace VMM that isn't aware of the per-VM ioctls, but
 doesn't seem too onerous to tell userspace "don't use these unless your entire fleet
 has upgraded", especially since that requirement/advisement is true for the KVM side
 with respect to new registers regardless of how those registers are accessed.
-_______________________________________________
-kvmarm mailing list
-kvmarm@lists.cs.columbia.edu
-https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
diff --git a/a/content_digest b/N2/content_digest
index 775f529..dc6e156 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -12,11 +12,20 @@
  "Subject\0Re: KVM/arm64: Guest ABI changes do not appear rollback-safe\0"
  "Date\0Tue, 8 Feb 2022 16:58:26 +0000\0"
  "To\0Oliver Upton <oupton@google.com>\0"
- "Cc\0kvm@vger.kernel.org"
-  Marc Zyngier <maz@kernel.org>
-  pshier@google.com
+ "Cc\0Marc Zyngier <maz@kernel.org>"
+  Raghavendra Rao Ananta <rananta@google.com>
+  Andrew Jones <drjones@redhat.com>
   kvmarm@lists.cs.columbia.edu
- " linux-arm-kernel@lists.infradead.org\0"
+  pshier@google.com
+  ricarkol@google.com
+  reijiw@google.com
+  jingzhangos@google.com
+  kvm@vger.kernel.org
+  linux-arm-kernel@lists.infradead.org
+  james.morse@arm.com
+  Alexandru.Elisei@arm.com
+  suzuki.poulose@arm.com
+ " Peter Maydell <peter.maydell@linaro.org>\0"
  "\00:1\0"
  "b\0"
  "On Tue, Feb 08, 2022, Oliver Upton wrote:\n"
@@ -54,10 +63,6 @@
  "ioctls is rollback to a userspace VMM that isn't aware of the per-VM ioctls, but it\n"
  "doesn't seem too onerous to tell userspace \"don't use these unless your entire fleet\n"
  "has upgraded\", especially since that requirement/advisement is true for the KVM side\n"
- "with respect to new registers regardless of how those registers are accessed.\n"
- "_______________________________________________\n"
- "kvmarm mailing list\n"
- "kvmarm@lists.cs.columbia.edu\n"
- https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
+ with respect to new registers regardless of how those registers are accessed.
 
-c6420d9e9568c0964ebf4e6503f7fea945ecbb18f14661e2a1f2cdb119bfdd0f
+2bfae2f6380791b0445c92b587c42ecd1f15cdd96d3fa7f6fe7d5b05220f4328

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.