All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20151027222706.GF7716@linux.vnet.ibm.com>

diff --git a/a/1.txt b/N1/1.txt
index bcc67bf..e5f027c 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -6,7 +6,7 @@ On 27.10.2015 [17:02:16 +1100], Alexey Kardashevskiy 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 74a5887..39d15be 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,9 +1,22 @@
  "ref\020151023205420.GA10197@linux.vnet.ibm.com\0"
  "ref\020151023205718.GC10197@linux.vnet.ibm.com\0"
  "ref\0562F1368.1030204@ozlabs.ru\0"
- "From\0nacc@linux.vnet.ibm.com (Nishanth Aravamudan)\0"
- "Subject\0[PATCH 2/7 v2] powerpc/dma-mapping: override dma_get_page_shift\0"
+ "From\0Nishanth Aravamudan <nacc@linux.vnet.ibm.com>\0"
+ "Subject\0Re: [PATCH 2/7 v2] powerpc/dma-mapping: override dma_get_page_shift\0"
  "Date\0Tue, 27 Oct 2015 15:27:06 -0700\0"
+ "To\0Alexey Kardashevskiy <aik@ozlabs.ru>\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 27.10.2015 [17:02:16 +1100], Alexey Kardashevskiy wrote:\n"
@@ -14,7 +27,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"
@@ -75,4 +88,4 @@
  "\n"
  -Nish
 
-3787d110a1eda4c579e7d9d297bef09ee493ab78cc004886c0e78ca20829787c
+5b405fa3b33aa5a3148c5da7e4f50afe6b156ecba788fa762ce3dad37b54476c

diff --git a/a/1.txt b/N2/1.txt
index bcc67bf..4ef9c0a 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -6,7 +6,7 @@ On 27.10.2015 [17:02:16 +1100], Alexey Kardashevskiy 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 +++++++++
@@ -43,7 +43,7 @@ On 27.10.2015 [17:02:16 +1100], Alexey Kardashevskiy 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:
@@ -53,7 +53,7 @@ PAGE_SHIFT everywhere, including Power.
 
 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.
 
@@ -62,7 +62,7 @@ get_dma_page_shift().
 
 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?
 
 -Nish
diff --git a/a/content_digest b/N2/content_digest
index 74a5887..ce7cf96 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -1,9 +1,10 @@
  "ref\020151023205420.GA10197@linux.vnet.ibm.com\0"
  "ref\020151023205718.GC10197@linux.vnet.ibm.com\0"
  "ref\0562F1368.1030204@ozlabs.ru\0"
- "From\0nacc@linux.vnet.ibm.com (Nishanth Aravamudan)\0"
- "Subject\0[PATCH 2/7 v2] powerpc/dma-mapping: override dma_get_page_shift\0"
- "Date\0Tue, 27 Oct 2015 15:27:06 -0700\0"
+ "From\0Nishanth Aravamudan <nacc@linux.vnet.ibm.com>\0"
+ "Subject\0Re: [PATCH 2/7 v2] powerpc/dma-mapping: override dma_get_page_shift\0"
+ "Date\0Tue, 27 Oct 2015 22:27:06 +0000\0"
+ "To\0sparclinux@vger.kernel.org\0"
  "\00:1\0"
  "b\0"
  "On 27.10.2015 [17:02:16 +1100], Alexey Kardashevskiy wrote:\n"
@@ -14,7 +15,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"
@@ -51,7 +52,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"
@@ -61,7 +62,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"
@@ -70,9 +71,9 @@
  "\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"
  -Nish
 
-3787d110a1eda4c579e7d9d297bef09ee493ab78cc004886c0e78ca20829787c
+6bebf8858f9a412d2712d8bc84a357a055c5545cda62e2197d25a3638c6c2a9e

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.