All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20151027140647.GA15583@localhost.localdomain>

diff --git a/a/1.txt b/N1/1.txt
index f865397..a95f664 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,4 +1,4 @@
-On Tue, Oct 27, 2015@05:02:16PM +1100, Alexey Kardashevskiy wrote:
+On Tue, Oct 27, 2015 at 05:02:16PM +1100, Alexey Kardashevskiy wrote:
 > >+unsigned long dma_get_page_shift(struct device *dev)
 > >+{
 > >+	struct iommu_table *tbl = get_iommu_table_base(dev);
diff --git a/a/content_digest b/N1/content_digest
index 0b637a9..3a5d9b7 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,12 +1,25 @@
  "ref\020151023205420.GA10197@linux.vnet.ibm.com\0"
  "ref\020151023205718.GC10197@linux.vnet.ibm.com\0"
  "ref\0562F1368.1030204@ozlabs.ru\0"
- "From\0keith.busch@intel.com (Busch, Keith)\0"
- "Subject\0[PATCH 2/7 v2] powerpc/dma-mapping: override dma_get_page_shift\0"
+ "From\0Busch, Keith <keith.busch@intel.com>\0"
+ "Subject\0Re: [PATCH 2/7 v2] powerpc/dma-mapping: override dma_get_page_shift\0"
  "Date\0Tue, 27 Oct 2015 14:06:47 +0000\0"
+ "To\0Alexey Kardashevskiy <aik@ozlabs.ru>\0"
+ "Cc\0Nishanth Aravamudan <nacc@linux.vnet.ibm.com>"
+  Michael Ellerman <mpe@ellerman.id.au>
+  Matthew Wilcox <willy@linux.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 Tue, Oct 27, 2015@05:02:16PM +1100, Alexey Kardashevskiy wrote:\n"
+ "On Tue, Oct 27, 2015 at 05:02:16PM +1100, Alexey Kardashevskiy wrote:\n"
  "> >+unsigned long dma_get_page_shift(struct device *dev)\n"
  "> >+{\n"
  "> >+\tstruct iommu_table *tbl = get_iommu_table_base(dev);\n"
@@ -24,4 +37,4 @@
  "which bits to mask from virtual addresses such that the offset is the\n"
  same as the DMA address.
 
-51cace80778f7e88b95d1b9dff11ccb42e43edc46e874729b85896cf15c0247d
+ff4fabac0ec34bb0f07de4cfdce245e8cea457be2abf5a82d4cd3b9bbabcaa4c

diff --git a/a/1.txt b/N2/1.txt
index f865397..d2ffa1b 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -1,4 +1,4 @@
-On Tue, Oct 27, 2015@05:02:16PM +1100, Alexey Kardashevskiy wrote:
+On Tue, Oct 27, 2015 at 05:02:16PM +1100, Alexey Kardashevskiy wrote:
 > >+unsigned long dma_get_page_shift(struct device *dev)
 > >+{
 > >+	struct iommu_table *tbl = get_iommu_table_base(dev);
@@ -8,7 +8,7 @@ On Tue, Oct 27, 2015@05:02:16PM +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?
 
 4k is always a safe option to return, but ideally you want to return the
diff --git a/a/content_digest b/N2/content_digest
index 0b637a9..762f971 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -1,12 +1,13 @@
  "ref\020151023205420.GA10197@linux.vnet.ibm.com\0"
  "ref\020151023205718.GC10197@linux.vnet.ibm.com\0"
  "ref\0562F1368.1030204@ozlabs.ru\0"
- "From\0keith.busch@intel.com (Busch, Keith)\0"
- "Subject\0[PATCH 2/7 v2] powerpc/dma-mapping: override dma_get_page_shift\0"
+ "From\0Busch, Keith <keith.busch@intel.com>\0"
+ "Subject\0Re: [PATCH 2/7 v2] powerpc/dma-mapping: override dma_get_page_shift\0"
  "Date\0Tue, 27 Oct 2015 14:06:47 +0000\0"
+ "To\0sparclinux@vger.kernel.org\0"
  "\00:1\0"
  "b\0"
- "On Tue, Oct 27, 2015@05:02:16PM +1100, Alexey Kardashevskiy wrote:\n"
+ "On Tue, Oct 27, 2015 at 05:02:16PM +1100, Alexey Kardashevskiy wrote:\n"
  "> >+unsigned long dma_get_page_shift(struct device *dev)\n"
  "> >+{\n"
  "> >+\tstruct iommu_table *tbl = get_iommu_table_base(dev);\n"
@@ -16,7 +17,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"
  "4k is always a safe option to return, but ideally you want to return the\n"
@@ -24,4 +25,4 @@
  "which bits to mask from virtual addresses such that the offset is the\n"
  same as the DMA address.
 
-51cace80778f7e88b95d1b9dff11ccb42e43edc46e874729b85896cf15c0247d
+33f2591f77a0dd41ddf927162ca2e38b83898f0336c6b2352f6f687379bea5fa

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.