All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <56301E24.1060304@ozlabs.ru>

diff --git a/a/1.txt b/N1/1.txt
index 81562e0..e89acfb 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -7,7 +7,7 @@ On 10/28/2015 09:27 AM, Nishanth Aravamudan wrote:
 >>> iommu_table, if available. Fallback to the kernel's page size,
 >>> otherwise.
 >>>
->>> Signed-off-by: Nishanth Aravamudan <nacc at linux.vnet.ibm.com>
+>>> Signed-off-by: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
 >>> ---
 >>>   arch/powerpc/include/asm/dma-mapping.h | 3 +++
 >>>   arch/powerpc/kernel/dma.c              | 9 +++++++++
diff --git a/a/content_digest b/N1/content_digest
index 25f3737..3112dc1 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -2,9 +2,22 @@
  "ref\020151023205718.GC10197@linux.vnet.ibm.com\0"
  "ref\0562F1368.1030204@ozlabs.ru\0"
  "ref\020151027222706.GF7716@linux.vnet.ibm.com\0"
- "From\0aik@ozlabs.ru (Alexey Kardashevskiy)\0"
- "Subject\0[PATCH 2/7 v2] powerpc/dma-mapping: override dma_get_page_shift\0"
+ "From\0Alexey Kardashevskiy <aik@ozlabs.ru>\0"
+ "Subject\0Re: [PATCH 2/7 v2] powerpc/dma-mapping: override dma_get_page_shift\0"
  "Date\0Wed, 28 Oct 2015 12:00:20 +1100\0"
+ "To\0Nishanth Aravamudan <nacc@linux.vnet.ibm.com>\0"
+ "Cc\0Michael Ellerman <mpe@ellerman.id.au>"
+  Matthew Wilcox <willy@linux.intel.com>
+  Keith Busch <keith.busch@intel.com>
+  Benjamin Herrenschmidt <benh@kernel.crashing.org>
+  Paul Mackerras <paulus@samba.org>
+  David Gibson <david@gibson.dropbear.id.au>
+  Christoph Hellwig <hch@infradead.org>
+  David S. Miller <davem@davemloft.net>
+  linux-nvme@lists.infradead.org
+  linux-kernel@vger.kernel.org
+  linuxppc-dev@lists.ozlabs.org
+ " sparclinux@vger.kernel.org\0"
  "\00:1\0"
  "b\0"
  "On 10/28/2015 09:27 AM, Nishanth Aravamudan wrote:\n"
@@ -16,7 +29,7 @@
  ">>> iommu_table, if available. Fallback to the kernel's page size,\n"
  ">>> otherwise.\n"
  ">>>\n"
- ">>> Signed-off-by: Nishanth Aravamudan <nacc at linux.vnet.ibm.com>\n"
+ ">>> Signed-off-by: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>\n"
  ">>> ---\n"
  ">>>   arch/powerpc/include/asm/dma-mapping.h | 3 +++\n"
  ">>>   arch/powerpc/kernel/dma.c              | 9 +++++++++\n"
@@ -90,4 +103,4 @@
  "-- \n"
  Alexey
 
-78cf7ae5e1ed98f309707aab5cb0a0b43b44ee184426865aa65ccbaf11a10b35
+794d77752bc16d79ed4cdb713ad99e932d094134cf0b2b1b78de8f5e0da05fbc

diff --git a/a/1.txt b/N2/1.txt
index 81562e0..cfd1a64 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -7,7 +7,7 @@ On 10/28/2015 09:27 AM, Nishanth Aravamudan wrote:
 >>> iommu_table, if available. Fallback to the kernel's page size,
 >>> otherwise.
 >>>
->>> Signed-off-by: Nishanth Aravamudan <nacc at linux.vnet.ibm.com>
+>>> Signed-off-by: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
 >>> ---
 >>>   arch/powerpc/include/asm/dma-mapping.h | 3 +++
 >>>   arch/powerpc/kernel/dma.c              | 9 +++++++++
@@ -44,7 +44,7 @@ On 10/28/2015 09:27 AM, Nishanth Aravamudan wrote:
 >>
 >> All PCI devices have this initialized on POWER (at least, our, IBM's
 >> POWER) so 4K will always be returned here while in the case of
->> (get_dma_ops(dev)==&dma_direct_ops) it could actually return
+>> (get_dma_ops(dev)=&dma_direct_ops) it could actually return
 >> PAGE_SHIFT. Is 4K still preferred value to return here?
 >
 > Right, so the logic of my series, goes like this:
@@ -54,7 +54,7 @@ On 10/28/2015 09:27 AM, Nishanth Aravamudan wrote:
 >
 > b) After 2/7, the Power code will return either the IOMMU table's shift
 > value, if set, or PAGE_SHIFT (I guess this would be the case if
-> get_dma_ops(dev) == &dma_direct_ops, as you said). That is no different
+> get_dma_ops(dev) = &dma_direct_ops, as you said). That is no different
 > than we have now, except we can return the accurate IOMMU value if
 > available.
 
@@ -69,7 +69,7 @@ function can ever return PAGE_SHIFT. imho.
 >
 > 4) After 4/7, pseries will return the DDW value, if available, then
 > fallback to the IOMMU table's value. I think in the case of
-> get_dma_ops(dev)==&dma_direct_ops, the only way that can happen is if we
+> get_dma_ops(dev)=&dma_direct_ops, the only way that can happen is if we
 > are using DDW, right?
 
 This is for pseries guests; for the powernv host it is a "bypass" mode 
diff --git a/a/content_digest b/N2/content_digest
index 25f3737..6f602d8 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -2,9 +2,10 @@
  "ref\020151023205718.GC10197@linux.vnet.ibm.com\0"
  "ref\0562F1368.1030204@ozlabs.ru\0"
  "ref\020151027222706.GF7716@linux.vnet.ibm.com\0"
- "From\0aik@ozlabs.ru (Alexey Kardashevskiy)\0"
- "Subject\0[PATCH 2/7 v2] powerpc/dma-mapping: override dma_get_page_shift\0"
- "Date\0Wed, 28 Oct 2015 12:00:20 +1100\0"
+ "From\0Alexey Kardashevskiy <aik@ozlabs.ru>\0"
+ "Subject\0Re: [PATCH 2/7 v2] powerpc/dma-mapping: override dma_get_page_shift\0"
+ "Date\0Wed, 28 Oct 2015 01:00:20 +0000\0"
+ "To\0sparclinux@vger.kernel.org\0"
  "\00:1\0"
  "b\0"
  "On 10/28/2015 09:27 AM, Nishanth Aravamudan wrote:\n"
@@ -16,7 +17,7 @@
  ">>> iommu_table, if available. Fallback to the kernel's page size,\n"
  ">>> otherwise.\n"
  ">>>\n"
- ">>> Signed-off-by: Nishanth Aravamudan <nacc at linux.vnet.ibm.com>\n"
+ ">>> Signed-off-by: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>\n"
  ">>> ---\n"
  ">>>   arch/powerpc/include/asm/dma-mapping.h | 3 +++\n"
  ">>>   arch/powerpc/kernel/dma.c              | 9 +++++++++\n"
@@ -53,7 +54,7 @@
  ">>\n"
  ">> All PCI devices have this initialized on POWER (at least, our, IBM's\n"
  ">> POWER) so 4K will always be returned here while in the case of\n"
- ">> (get_dma_ops(dev)==&dma_direct_ops) it could actually return\n"
+ ">> (get_dma_ops(dev)=&dma_direct_ops) it could actually return\n"
  ">> PAGE_SHIFT. Is 4K still preferred value to return here?\n"
  ">\n"
  "> Right, so the logic of my series, goes like this:\n"
@@ -63,7 +64,7 @@
  ">\n"
  "> b) After 2/7, the Power code will return either the IOMMU table's shift\n"
  "> value, if set, or PAGE_SHIFT (I guess this would be the case if\n"
- "> get_dma_ops(dev) == &dma_direct_ops, as you said). That is no different\n"
+ "> get_dma_ops(dev) = &dma_direct_ops, as you said). That is no different\n"
  "> than we have now, except we can return the accurate IOMMU value if\n"
  "> available.\n"
  "\n"
@@ -78,7 +79,7 @@
  ">\n"
  "> 4) After 4/7, pseries will return the DDW value, if available, then\n"
  "> fallback to the IOMMU table's value. I think in the case of\n"
- "> get_dma_ops(dev)==&dma_direct_ops, the only way that can happen is if we\n"
+ "> get_dma_ops(dev)=&dma_direct_ops, the only way that can happen is if we\n"
  "> are using DDW, right?\n"
  "\n"
  "This is for pseries guests; for the powernv host it is a \"bypass\" mode \n"
@@ -90,4 +91,4 @@
  "-- \n"
  Alexey
 
-78cf7ae5e1ed98f309707aab5cb0a0b43b44ee184426865aa65ccbaf11a10b35
+7f8d6b28561e1ec3ee98f797efa536d22a40ca2a8963d51795c38312a4ec6cdc

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.