diff for duplicates of <20160916122937.GA14140@cbox>

diff --git a/a/1.txt b/N1/1.txt
index e8241d8..57cf62a 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -29,7 +29,7 @@ On Fri, Sep 16, 2016 at 02:25:01PM +0200, Alexander Graf wrote:
 > > fairly obvious that this kind of sub-standard HW will eventually
 > > disappear. We'll then be left with a userspace ABI that will break at
 > 
-> I’m not 100% convinced that this is the case. Emulating the GIC in user space can have other interesting use cases. For example, it might come in handy for nesting. It may be useful for migrating a gicv2 VM to a gicv3 host without gicv2 emulation as well.
+> I?m not 100% convinced that this is the case. Emulating the GIC in user space can have other interesting use cases. For example, it might come in handy for nesting. It may be useful for migrating a gicv2 VM to a gicv3 host without gicv2 emulation as well.
 > 
 
 I don't see why you'd do this; the VGIC hardware can perfectly well be
@@ -38,7 +38,7 @@ used for nesting as well, and this works rather well.
 > > every single release, given that nobody in the RPi community actually
 > > uses a mainline kernel.
 > 
-> I actually verified all of this patch on 4.8-rc5 upstream, which is the only 64bit kernel you can find for the RPi. So I’d expect the situation to change with 64bit.
+> I actually verified all of this patch on 4.8-rc5 upstream, which is the only 64bit kernel you can find for the RPi. So I?d expect the situation to change with 64bit.
 > 
 > > And breaking this ABI will introduce userspace exploitable bugs, like
 > > the one you've already shown. If anything, I would have loved to
@@ -51,7 +51,7 @@ used for nesting as well, and this works rather well.
 > > You could still run KVM with an external emulated timer (not the arch
 > > timer). No need for a new ABI for that.
 > 
-> That’s what I thought too, but turns out that it’s not quite as simple as I hoped ;).
+> That?s what I thought too, but turns out that it?s not quite as simple as I hoped ;).
 
 Why not?  I thought a few people had this running recently.  What were
 the issues?  Perhaps I can convince someone to submit the patches they
@@ -59,7 +59,3 @@ used if useful.
 
 Thanks,
 -Christoffer
-_______________________________________________
-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 2390dcf..464de2b 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,14 +1,10 @@
  "ref\01474007187-18673-1-git-send-email-agraf@suse.de\0"
  "ref\057DBC782.7080305@arm.com\0"
  "ref\0060ADA14-786E-400E-9B11-61C34B7081B5@suse.de\0"
- "From\0Christoffer Dall <christoffer.dall@linaro.org>\0"
- "Subject\0Re: [PATCH v3 0/2] KVM: ARM: Enable vtimers with user space gic\0"
+ "From\0christoffer.dall@linaro.org (Christoffer Dall)\0"
+ "Subject\0[PATCH v3 0/2] KVM: ARM: Enable vtimers with user space gic\0"
  "Date\0Fri, 16 Sep 2016 14:29:37 +0200\0"
- "To\0Alexander Graf <agraf@suse.de>\0"
- "Cc\0Marc Zyngier <marc.zyngier@arm.com>"
-  kvmarm@lists.cs.columbia.edu
-  kvm@vger.kernel.org
- " linux-arm-kernel@lists.infradead.org\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "On Fri, Sep 16, 2016 at 02:25:01PM +0200, Alexander Graf wrote:\n"
@@ -42,7 +38,7 @@
  "> > fairly obvious that this kind of sub-standard HW will eventually\n"
  "> > disappear. We'll then be left with a userspace ABI that will break at\n"
  "> \n"
- "> I\342\200\231m not 100% convinced that this is the case. Emulating the GIC in user space can have other interesting use cases. For example, it might come in handy for nesting. It may be useful for migrating a gicv2 VM to a gicv3 host without gicv2 emulation as well.\n"
+ "> I?m not 100% convinced that this is the case. Emulating the GIC in user space can have other interesting use cases. For example, it might come in handy for nesting. It may be useful for migrating a gicv2 VM to a gicv3 host without gicv2 emulation as well.\n"
  "> \n"
  "\n"
  "I don't see why you'd do this; the VGIC hardware can perfectly well be\n"
@@ -51,7 +47,7 @@
  "> > every single release, given that nobody in the RPi community actually\n"
  "> > uses a mainline kernel.\n"
  "> \n"
- "> I actually verified all of this patch on 4.8-rc5 upstream, which is the only 64bit kernel you can find for the RPi. So I\342\200\231d expect the situation to change with 64bit.\n"
+ "> I actually verified all of this patch on 4.8-rc5 upstream, which is the only 64bit kernel you can find for the RPi. So I?d expect the situation to change with 64bit.\n"
  "> \n"
  "> > And breaking this ABI will introduce userspace exploitable bugs, like\n"
  "> > the one you've already shown. If anything, I would have loved to\n"
@@ -64,17 +60,13 @@
  "> > You could still run KVM with an external emulated timer (not the arch\n"
  "> > timer). No need for a new ABI for that.\n"
  "> \n"
- "> That\342\200\231s what I thought too, but turns out that it\342\200\231s not quite as simple as I hoped ;).\n"
+ "> That?s what I thought too, but turns out that it?s not quite as simple as I hoped ;).\n"
  "\n"
  "Why not?  I thought a few people had this running recently.  What were\n"
  "the issues?  Perhaps I can convince someone to submit the patches they\n"
  "used if useful.\n"
  "\n"
  "Thanks,\n"
- "-Christoffer\n"
- "_______________________________________________\n"
- "kvmarm mailing list\n"
- "kvmarm@lists.cs.columbia.edu\n"
- https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
+ -Christoffer
 
-3807eef3a537e1f78b13c10280b08e5ea371ffe7175ce5afc6a49148fe2506a9
+098346c8fa0b1dd739746018efec3b8d3fde8e15bbcbb40bc54bfda213a87a8f
