All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <55B8E866.60308@oracle.com>

diff --git a/a/1.txt b/N1/1.txt
index 605cb2c..1fef796 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -29,7 +29,8 @@ Right, and my comments were also not about correctness.
 >
 > Anyway, the oddity of mfn = pfn_to_gfn(...) is mostly contained in the
 > x86 specific code. I don't mind to either add pfn_to_mfn and use it or
-> add a comment /* PV-specific so mfn = gfn */ for every use of mfn > pfn_to_gfn(...).
+> add a comment /* PV-specific so mfn == gfn */ for every use of mfn =
+> pfn_to_gfn(...).
 
 I think the former is better (even thought it adds a test)
 
diff --git a/a/content_digest b/N1/content_digest
index d9edffa..c1a5de0 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -6,8 +6,33 @@
  "ref\055B8E1C7.6070608@citrix.com\0"
  "From\0Boris Ostrovsky <boris.ostrovsky@oracle.com>\0"
  "Subject\0Re: [PATCH 4/8] xen: Use the correctly the Xen memory terminologies\0"
- "Date\0Wed, 29 Jul 2015 14:51:18 +0000\0"
- "To\0linux-arm-kernel@lists.infradead.org\0"
+ "Date\0Wed, 29 Jul 2015 10:51:18 -0400\0"
+ "To\0Julien Grall <julien.grall@citrix.com>"
+ " xen-devel@lists.xenproject.org\0"
+ "Cc\0linux-fbdev@vger.kernel.org"
+  H. Peter Anvin <hpa@zytor.com>
+  Jiri Slaby <jslaby@suse.com>
+  stefano.stabellini@eu.citrix.com
+  Russell King <linux@arm.linux.org.uk>
+  linux-scsi@vger.kernel.org
+  x86@kernel.org
+  Tomi Valkeinen <tomi.valkeinen@ti.com>
+  linux-input@vger.kernel.org
+  Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>
+  ian.campbell@citrix.com
+  Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
+  James E.J. Bottomley <JBottomley@odin.com>
+  Thomas Gleixner <tglx@linutronix.de>
+  Ingo Molnar <mingo@redhat.com>
+  linux-arm-kernel@lists.infradead.org
+  Juergen Gross <jgross@suse.com>
+  Wei Liu <wei.liu2@citrix.com>
+  Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+  Dmitry Torokhov <dmitry.torokhov@gmail.com>
+  linux-kernel@vger.kernel.org
+  David Vrabel <david.vrabel@citrix.com>
+  netdev@vger.kernel.org
+ " linuxppc-dev@lists.ozlabs.org\0"
  "\00:1\0"
  "b\0"
  "On 07/29/2015 10:23 AM, Julien Grall wrote:\n"
@@ -41,10 +66,11 @@
  ">\n"
  "> Anyway, the oddity of mfn = pfn_to_gfn(...) is mostly contained in the\n"
  "> x86 specific code. I don't mind to either add pfn_to_mfn and use it or\n"
- "> add a comment /* PV-specific so mfn = gfn */ for every use of mfn > pfn_to_gfn(...).\n"
+ "> add a comment /* PV-specific so mfn == gfn */ for every use of mfn =\n"
+ "> pfn_to_gfn(...).\n"
  "\n"
  "I think the former is better (even thought it adds a test)\n"
  "\n"
  -boris
 
-f4f6f38317b5a29c3fbde09d0c00610a7db3045798b3f584c055e70cbc5f351b
+966fc406e2a51c7b11389bbc0bd5ab4a7680aae880510390c738f9f924b9b30d

diff --git a/a/1.txt b/N2/1.txt
index 605cb2c..1fef796 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -29,7 +29,8 @@ Right, and my comments were also not about correctness.
 >
 > Anyway, the oddity of mfn = pfn_to_gfn(...) is mostly contained in the
 > x86 specific code. I don't mind to either add pfn_to_mfn and use it or
-> add a comment /* PV-specific so mfn = gfn */ for every use of mfn > pfn_to_gfn(...).
+> add a comment /* PV-specific so mfn == gfn */ for every use of mfn =
+> pfn_to_gfn(...).
 
 I think the former is better (even thought it adds a test)
 
diff --git a/a/content_digest b/N2/content_digest
index d9edffa..9be04fc 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -6,8 +6,34 @@
  "ref\055B8E1C7.6070608@citrix.com\0"
  "From\0Boris Ostrovsky <boris.ostrovsky@oracle.com>\0"
  "Subject\0Re: [PATCH 4/8] xen: Use the correctly the Xen memory terminologies\0"
- "Date\0Wed, 29 Jul 2015 14:51:18 +0000\0"
- "To\0linux-arm-kernel@lists.infradead.org\0"
+ "Date\0Wed, 29 Jul 2015 10:51:18 -0400\0"
+ "To\0Julien Grall <julien.grall@citrix.com>"
+ " xen-devel@lists.xenproject.org\0"
+ "Cc\0linux-fbdev@vger.kernel.org"
+  H. Peter Anvin <hpa@zytor.com>
+  Jiri Slaby <jslaby@suse.com>
+  stefano.stabellini@eu.citrix.com
+  Russell King <linux@arm.linux.org.uk>
+  linux-scsi@vger.kernel.org
+  x86@kernel.org
+  Tomi Valkeinen <tomi.valkeinen@ti.com>
+  linux-input@vger.kernel.org
+  Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>
+  ian.campbell@citrix.com
+  Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
+  James E.J. Bottomley <JBottomley@odin.com>
+  Thomas Gleixner <tglx@linutronix.de>
+  Ingo Molnar <mingo@redhat.com>
+  linux-arm-kernel@lists.infradead.org
+  Juergen Gross <jgross@suse.com>
+  Wei Liu <wei.liu2@citrix.com>
+  Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+  Dmitry Torokhov <dmitry.torokhov@gmail.com>
+  linux-kernel@vger.kernel.org
+  David Vrabel <david.vrabel@citrix.com>
+  netdev@vger.kernel.org
+  linuxppc-dev@lists.ozlabs.org
+ " Roger Pau Monn\303\251 <roger.pau@citrix.com>\0"
  "\00:1\0"
  "b\0"
  "On 07/29/2015 10:23 AM, Julien Grall wrote:\n"
@@ -41,10 +67,11 @@
  ">\n"
  "> Anyway, the oddity of mfn = pfn_to_gfn(...) is mostly contained in the\n"
  "> x86 specific code. I don't mind to either add pfn_to_mfn and use it or\n"
- "> add a comment /* PV-specific so mfn = gfn */ for every use of mfn > pfn_to_gfn(...).\n"
+ "> add a comment /* PV-specific so mfn == gfn */ for every use of mfn =\n"
+ "> pfn_to_gfn(...).\n"
  "\n"
  "I think the former is better (even thought it adds a test)\n"
  "\n"
  -boris
 
-f4f6f38317b5a29c3fbde09d0c00610a7db3045798b3f584c055e70cbc5f351b
+93529937c7a569314e35f5baf94042c136ce3a3a42d0f84757e0aa87b9a4bc5f

diff --git a/a/1.txt b/N3/1.txt
index 605cb2c..1fef796 100644
--- a/a/1.txt
+++ b/N3/1.txt
@@ -29,7 +29,8 @@ Right, and my comments were also not about correctness.
 >
 > Anyway, the oddity of mfn = pfn_to_gfn(...) is mostly contained in the
 > x86 specific code. I don't mind to either add pfn_to_mfn and use it or
-> add a comment /* PV-specific so mfn = gfn */ for every use of mfn > pfn_to_gfn(...).
+> add a comment /* PV-specific so mfn == gfn */ for every use of mfn =
+> pfn_to_gfn(...).
 
 I think the former is better (even thought it adds a test)
 
diff --git a/a/content_digest b/N3/content_digest
index d9edffa..add8d60 100644
--- a/a/content_digest
+++ b/N3/content_digest
@@ -4,9 +4,9 @@
  "ref\055B8B846.2060103@citrix.com\0"
  "ref\055B8DFD7.6070107@oracle.com\0"
  "ref\055B8E1C7.6070608@citrix.com\0"
- "From\0Boris Ostrovsky <boris.ostrovsky@oracle.com>\0"
- "Subject\0Re: [PATCH 4/8] xen: Use the correctly the Xen memory terminologies\0"
- "Date\0Wed, 29 Jul 2015 14:51:18 +0000\0"
+ "From\0boris.ostrovsky@oracle.com (Boris Ostrovsky)\0"
+ "Subject\0[PATCH 4/8] xen: Use the correctly the Xen memory terminologies\0"
+ "Date\0Wed, 29 Jul 2015 10:51:18 -0400\0"
  "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
@@ -41,10 +41,11 @@
  ">\n"
  "> Anyway, the oddity of mfn = pfn_to_gfn(...) is mostly contained in the\n"
  "> x86 specific code. I don't mind to either add pfn_to_mfn and use it or\n"
- "> add a comment /* PV-specific so mfn = gfn */ for every use of mfn > pfn_to_gfn(...).\n"
+ "> add a comment /* PV-specific so mfn == gfn */ for every use of mfn =\n"
+ "> pfn_to_gfn(...).\n"
  "\n"
  "I think the former is better (even thought it adds a test)\n"
  "\n"
  -boris
 
-f4f6f38317b5a29c3fbde09d0c00610a7db3045798b3f584c055e70cbc5f351b
+63650fd91ab97dec5aac74b878ba13a2a74fa3cc1434aebc4b47e2878ec13442

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.