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

diff --git a/a/1.txt b/N1/1.txt
index 3462651..65695a8 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,5 +1,5 @@
 On 03.10.2015 [07:35:09 +1000], Benjamin Herrenschmidt wrote:
-> On Fri, 2015-10-02@14:04 -0700, Nishanth Aravamudan wrote:
+> On Fri, 2015-10-02 at 14:04 -0700, Nishanth Aravamudan wrote:
 > > Right, I did start with your advice and tried that approach, but it
 > > turned out I was wrong about the actual issue at the time. The problem
 > > for NVMe isn't actually the starting address alignment (which it can
diff --git a/a/content_digest b/N1/content_digest
index c291e85..1833c8a 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -3,13 +3,24 @@
  "ref\01443819066.27295.19.camel@kernel.crashing.org\0"
  "ref\020151002210435.GM8040@linux.vnet.ibm.com\0"
  "ref\01443821709.27295.20.camel@kernel.crashing.org\0"
- "From\0nacc@linux.vnet.ibm.com (Nishanth Aravamudan)\0"
- "Subject\0[PATCH 0/5 v2] Fix NVMe driver support on Power with 32-bit DMA\0"
+ "From\0Nishanth Aravamudan <nacc@linux.vnet.ibm.com>\0"
+ "Subject\0Re: [PATCH 0/5 v2] Fix NVMe driver support on Power with 32-bit DMA\0"
  "Date\0Fri, 2 Oct 2015 14:48:00 -0700\0"
+ "To\0Benjamin Herrenschmidt <benh@kernel.crashing.org>\0"
+ "Cc\0Matthew Wilcox <willy@linux.intel.com>"
+  Keith Busch <keith.busch@intel.com>
+  Paul Mackerras <paulus@samba.org>
+  Michael Ellerman <mpe@ellerman.id.au>
+  Alexey Kardashevskiy <aik@ozlabs.ru>
+  David Gibson <david@gibson.dropbear.id.au>
+  Christoph Hellwig <hch@infradead.org>
+  linux-nvme@lists.infradead.org
+  linux-kernel@vger.kernel.org
+ " linuxppc-dev@lists.ozlabs.org\0"
  "\00:1\0"
  "b\0"
  "On 03.10.2015 [07:35:09 +1000], Benjamin Herrenschmidt wrote:\n"
- "> On Fri, 2015-10-02@14:04 -0700, Nishanth Aravamudan wrote:\n"
+ "> On Fri, 2015-10-02 at 14:04 -0700, Nishanth Aravamudan wrote:\n"
  "> > Right, I did start with your advice and tried that approach, but it\n"
  "> > turned out I was wrong about the actual issue at the time. The problem\n"
  "> > for NVMe isn't actually the starting address alignment (which it can\n"
@@ -38,4 +49,4 @@
  "\n"
  -Nish
 
-bfc52105158ed0d26a75b4c6c8c2f5bb07c6e9b56a4543a230873695a6566d00
+10118a08763a8918488f24d874ca3d15a659a6b5897a58ca108e0b5382da8e3e

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.