All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20181220144604.GA18034@lst.de>

diff --git a/a/content_digest b/N1/content_digest
index afad52e..b191a67 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -19,7 +19,9 @@
   openrisc@lists.librecores.org <openrisc@lists.librecores.org>
   ashutosh.dixit@intel.com <ashutosh.dixit@intel.com>
   linux-parisc@vger.kernel.org <linux-parisc@vger.kernel.org>
- " linux-c6x-dev@linux-c6x.org <linux-c6x-dev@linux-c6x.org>\0"
+  linux-c6x-dev@linux-c6x.org <linux-c6x-dev@linux-c6x.org>
+  monstr@monstr.eu <monstr@monstr.eu>
+ " sparclinux@vger.kernel.org <sparclinux@vger.kernel.org>\0"
  "\00:1\0"
  "b\0"
  "On Thu, Dec 20, 2018 at 02:39:20PM +0000, Eugeniy Paltsev wrote:\n"
@@ -37,4 +39,4 @@
  "just before the zeroing to start, and if that is already broken (which\n"
  I suspect) bisect the offending commit?
 
-153ef12c1f93761e26e8d8d3312d9069c8d632b5c4011ad7066a523309a55ba0
+73b04a11935ba3afdc99ae2d4d30ced66ebee8d8066025ae87b05a723f135c3c

diff --git a/a/1.txt b/N2/1.txt
index c95404c..b9aa299 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -1,4 +1,4 @@
-On Thu, Dec 20, 2018 at 02:39:20PM +0000, Eugeniy Paltsev wrote:
+On Thu, Dec 20, 2018@02:39:20PM +0000, Eugeniy Paltsev wrote:
 > > I would be really surprised if that is caused by the patch to add
 > > the zeroing. 
 > Me too :)
diff --git a/a/content_digest b/N2/content_digest
index afad52e..77b5f1b 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -3,26 +3,13 @@
  "ref\01545316369.14089.20.camel@synopsys.com\0"
  "ref\020181220143415.GA17726@lst.de\0"
  "ref\01545316759.14089.22.camel@synopsys.com\0"
- "From\0hch@lst.de <hch@lst.de>\0"
- "Subject\0Re: ensure dma_alloc_coherent always returns zeroed memory\0"
+ "From\0hch@lst.de (hch@lst.de)\0"
+ "Subject\0ensure dma_alloc_coherent always returns zeroed memory\0"
  "Date\0Thu, 20 Dec 2018 15:46:04 +0100\0"
- "To\0Eugeniy Paltsev <eugeniy.paltsev@synopsys.com>\0"
- "Cc\0hch@lst.de <hch@lst.de>"
-  linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>
-  linux-s390@vger.kernel.org <linux-s390@vger.kernel.org>
-  linux-xtensa@linux-xtensa.org <linux-xtensa@linux-xtensa.org>
-  linux-m68k@lists.linux-m68k.org <linux-m68k@lists.linux-m68k.org>
-  vineet.gupta1@synopsys.com <vineet.gupta1@synopsys.com>
-  linux-alpha@vger.kernel.org <linux-alpha@vger.kernel.org>
-  linux-snps-arc@lists.infradead.org <linux-snps-arc@lists.infradead.org>
-  iommu@lists.linux-foundation.org <iommu@lists.linux-foundation.org>
-  openrisc@lists.librecores.org <openrisc@lists.librecores.org>
-  ashutosh.dixit@intel.com <ashutosh.dixit@intel.com>
-  linux-parisc@vger.kernel.org <linux-parisc@vger.kernel.org>
- " linux-c6x-dev@linux-c6x.org <linux-c6x-dev@linux-c6x.org>\0"
+ "To\0linux-snps-arc@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
- "On Thu, Dec 20, 2018 at 02:39:20PM +0000, Eugeniy Paltsev wrote:\n"
+ "On Thu, Dec 20, 2018@02:39:20PM +0000, Eugeniy Paltsev wrote:\n"
  "> > I would be really surprised if that is caused by the patch to add\n"
  "> > the zeroing. \n"
  "> Me too :)\n"
@@ -37,4 +24,4 @@
  "just before the zeroing to start, and if that is already broken (which\n"
  I suspect) bisect the offending commit?
 
-153ef12c1f93761e26e8d8d3312d9069c8d632b5c4011ad7066a523309a55ba0
+a6cef4b643ce9b4f15d3df0f3fa59eeec398f1e610dee46e40297f2244f4473e

diff --git a/a/content_digest b/N3/content_digest
index afad52e..4b9e3a6 100644
--- a/a/content_digest
+++ b/N3/content_digest
@@ -4,22 +4,9 @@
  "ref\020181220143415.GA17726@lst.de\0"
  "ref\01545316759.14089.22.camel@synopsys.com\0"
  "From\0hch@lst.de <hch@lst.de>\0"
- "Subject\0Re: ensure dma_alloc_coherent always returns zeroed memory\0"
+ "Subject\0[OpenRISC] ensure dma_alloc_coherent always returns zeroed memory\0"
  "Date\0Thu, 20 Dec 2018 15:46:04 +0100\0"
- "To\0Eugeniy Paltsev <eugeniy.paltsev@synopsys.com>\0"
- "Cc\0hch@lst.de <hch@lst.de>"
-  linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>
-  linux-s390@vger.kernel.org <linux-s390@vger.kernel.org>
-  linux-xtensa@linux-xtensa.org <linux-xtensa@linux-xtensa.org>
-  linux-m68k@lists.linux-m68k.org <linux-m68k@lists.linux-m68k.org>
-  vineet.gupta1@synopsys.com <vineet.gupta1@synopsys.com>
-  linux-alpha@vger.kernel.org <linux-alpha@vger.kernel.org>
-  linux-snps-arc@lists.infradead.org <linux-snps-arc@lists.infradead.org>
-  iommu@lists.linux-foundation.org <iommu@lists.linux-foundation.org>
-  openrisc@lists.librecores.org <openrisc@lists.librecores.org>
-  ashutosh.dixit@intel.com <ashutosh.dixit@intel.com>
-  linux-parisc@vger.kernel.org <linux-parisc@vger.kernel.org>
- " linux-c6x-dev@linux-c6x.org <linux-c6x-dev@linux-c6x.org>\0"
+ "To\0openrisc@lists.librecores.org\0"
  "\00:1\0"
  "b\0"
  "On Thu, Dec 20, 2018 at 02:39:20PM +0000, Eugeniy Paltsev wrote:\n"
@@ -37,4 +24,4 @@
  "just before the zeroing to start, and if that is already broken (which\n"
  I suspect) bisect the offending commit?
 
-153ef12c1f93761e26e8d8d3312d9069c8d632b5c4011ad7066a523309a55ba0
+2c3ed05fe45bb913e7eea7368b1a2d76bdb49002ac9bfcf1b47e0e1130edc426

diff --git a/a/content_digest b/N4/content_digest
index afad52e..fa74184 100644
--- a/a/content_digest
+++ b/N4/content_digest
@@ -5,7 +5,7 @@
  "ref\01545316759.14089.22.camel@synopsys.com\0"
  "From\0hch@lst.de <hch@lst.de>\0"
  "Subject\0Re: ensure dma_alloc_coherent always returns zeroed memory\0"
- "Date\0Thu, 20 Dec 2018 15:46:04 +0100\0"
+ "Date\0Thu, 20 Dec 2018 14:46:04 +0000\0"
  "To\0Eugeniy Paltsev <eugeniy.paltsev@synopsys.com>\0"
  "Cc\0hch@lst.de <hch@lst.de>"
   linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>
@@ -37,4 +37,4 @@
  "just before the zeroing to start, and if that is already broken (which\n"
  I suspect) bisect the offending commit?
 
-153ef12c1f93761e26e8d8d3312d9069c8d632b5c4011ad7066a523309a55ba0
+77ad59cc36ae7a5bc765616e37760c4293d98e600cba9307f1f319000f90ae3d

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.