All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20130923183401.GE1445@redhat.com>

diff --git a/a/1.txt b/N1/1.txt
index d42256a..4dc13f4 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -4,7 +4,7 @@ On Mon, Sep 23, 2013 at 09:24:14PM +1000, Paul Mackerras wrote:
 > > > This implements a simple way to express the case of IRQ routing where
 > > > there is one in-kernel PIC and the system interrupts (GSIs) are routed
 > > > 1-1 to the corresponding pins of the PIC.  This is expressed by having
-> > > kvm->irq_routing = NULL with a skeleton irq routing entry in the new
+> > > kvm->irq_routing == NULL with a skeleton irq routing entry in the new
 > > > kvm->default_irq_route field.
 > > > 
 > > > This provides a convenient way to provide backwards compatibility when
@@ -12,7 +12,7 @@ On Mon, Sep 23, 2013 at 09:24:14PM +1000, Paul Mackerras wrote:
 > > > XICS emulation on powerpc.
 > > > 
 > > Why not create simple 1-1 irq routing table? It will take a little bit
-> > more memory, but there will be no need for kvm->irq_routing = NULL
+> > more memory, but there will be no need for kvm->irq_routing == NULL
 > > special handling.
 > 
 > The short answer is that userspace wants to use interrupt source
diff --git a/a/content_digest b/N1/content_digest
index 3639e43..28d98a8 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -3,7 +3,7 @@
  "ref\020130923112414.GA32420@iris.ozlabs.ibm.com\0"
  "From\0Gleb Natapov <gleb@redhat.com>\0"
  "Subject\0Re: [PATCH 1/2] KVM: Implement default IRQ routing\0"
- "Date\0Mon, 23 Sep 2013 18:34:01 +0000\0"
+ "Date\0Mon, 23 Sep 2013 21:34:01 +0300\0"
  "To\0Paul Mackerras <paulus@samba.org>\0"
  "Cc\0kvm@vger.kernel.org"
   kvm-ppc@vger.kernel.org
@@ -17,7 +17,7 @@
  "> > > This implements a simple way to express the case of IRQ routing where\n"
  "> > > there is one in-kernel PIC and the system interrupts (GSIs) are routed\n"
  "> > > 1-1 to the corresponding pins of the PIC.  This is expressed by having\n"
- "> > > kvm->irq_routing = NULL with a skeleton irq routing entry in the new\n"
+ "> > > kvm->irq_routing == NULL with a skeleton irq routing entry in the new\n"
  "> > > kvm->default_irq_route field.\n"
  "> > > \n"
  "> > > This provides a convenient way to provide backwards compatibility when\n"
@@ -25,7 +25,7 @@
  "> > > XICS emulation on powerpc.\n"
  "> > > \n"
  "> > Why not create simple 1-1 irq routing table? It will take a little bit\n"
- "> > more memory, but there will be no need for kvm->irq_routing = NULL\n"
+ "> > more memory, but there will be no need for kvm->irq_routing == NULL\n"
  "> > special handling.\n"
  "> \n"
  "> The short answer is that userspace wants to use interrupt source\n"
@@ -69,4 +69,4 @@
  "--\n"
  "\t\t\tGleb."
 
-a4735834cbe1297590ee8eba00c2af4f90ca706d5c8f5e9e97bf6f5dd4fa2aa3
+fd5e38f7562ca9c2c34f6b77f2039add0d7a6b70c5d05fc242f68236dc075e90

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.