diff for duplicates of <20181220143415.GA17726@lst.de> diff --git a/a/content_digest b/N1/content_digest index 38071bd..1e2a21d 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -18,7 +18,8 @@ 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> - " monst\0" + 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:32:52PM +0000, Eugeniy Paltsev wrote:\n" @@ -31,4 +32,4 @@ "the zeroing. Can you check which commit caused the issue by bisecting\n" from a known good baseline? -b4be351fc33611134d783a41b1463e8e8d6eb3414c96b7c52cfa29ab36bfefee +971ddb39f88e4e846b9d45d8db16764cbb9913a235c8d8f8c372a3e16b3401f9
diff --git a/a/1.txt b/N2/1.txt index 7340a62..81e917a 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,4 +1,4 @@ -On Thu, Dec 20, 2018 at 02:32:52PM +0000, Eugeniy Paltsev wrote: +On Thu, Dec 20, 2018@02:32:52PM +0000, Eugeniy Paltsev wrote: > Hi Christoph, > > I test kernel from your 'dma-alloc-always-zero' branch, and as diff --git a/a/content_digest b/N2/content_digest index 38071bd..bc69d2a 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,27 +1,13 @@ "ref\020181214082515.14835-1-hch@lst.de\0" "ref\020181219165939.GA26087@lst.de\0" "ref\01545316369.14089.20.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:34:15 +0100\0" - "To\0Eugeniy Paltsev <eugeniy.paltsev@synopsys.com>\0" - "Cc\0hch@lst.de <hch@lst.de>" - Vineet Gupta <vineet.gupta1@synopsys.com> - iommu@lists.linux-foundation.org <iommu@lists.linux-foundation.org> - 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> - linux-alpha@vger.kernel.org <linux-alpha@vger.kernel.org> - linux-snps-arc@lists.infradead.org <linux-snps-arc@lists.infradead.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> - " monst\0" + "To\0linux-snps-arc@lists.infradead.org\0" "\00:1\0" "b\0" - "On Thu, Dec 20, 2018 at 02:32:52PM +0000, Eugeniy Paltsev wrote:\n" + "On Thu, Dec 20, 2018@02:32:52PM +0000, Eugeniy Paltsev wrote:\n" "> Hi Christoph,\n" "> \n" "> I test kernel from your 'dma-alloc-always-zero' branch, and as\n" @@ -31,4 +17,4 @@ "the zeroing. Can you check which commit caused the issue by bisecting\n" from a known good baseline? -b4be351fc33611134d783a41b1463e8e8d6eb3414c96b7c52cfa29ab36bfefee +05181affd513f952327b30649f6a3c56b76a85336f97d9c539c0893712ed0baa
diff --git a/a/content_digest b/N3/content_digest index 38071bd..b252317 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -2,23 +2,9 @@ "ref\020181219165939.GA26087@lst.de\0" "ref\01545316369.14089.20.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:34:15 +0100\0" - "To\0Eugeniy Paltsev <eugeniy.paltsev@synopsys.com>\0" - "Cc\0hch@lst.de <hch@lst.de>" - Vineet Gupta <vineet.gupta1@synopsys.com> - iommu@lists.linux-foundation.org <iommu@lists.linux-foundation.org> - 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> - linux-alpha@vger.kernel.org <linux-alpha@vger.kernel.org> - linux-snps-arc@lists.infradead.org <linux-snps-arc@lists.infradead.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> - " monst\0" + "To\0openrisc@lists.librecores.org\0" "\00:1\0" "b\0" "On Thu, Dec 20, 2018 at 02:32:52PM +0000, Eugeniy Paltsev wrote:\n" @@ -31,4 +17,4 @@ "the zeroing. Can you check which commit caused the issue by bisecting\n" from a known good baseline? -b4be351fc33611134d783a41b1463e8e8d6eb3414c96b7c52cfa29ab36bfefee +1b1e0686a5be75435193335b4f93a78860104edd960cb049a489bb12c92dd0e5
diff --git a/a/content_digest b/N4/content_digest index 38071bd..4dc51e6 100644 --- a/a/content_digest +++ b/N4/content_digest @@ -3,7 +3,7 @@ "ref\01545316369.14089.20.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:34:15 +0100\0" + "Date\0Thu, 20 Dec 2018 14:34:15 +0000\0" "To\0Eugeniy Paltsev <eugeniy.paltsev@synopsys.com>\0" "Cc\0hch@lst.de <hch@lst.de>" Vineet Gupta <vineet.gupta1@synopsys.com> @@ -31,4 +31,4 @@ "the zeroing. Can you check which commit caused the issue by bisecting\n" from a known good baseline? -b4be351fc33611134d783a41b1463e8e8d6eb3414c96b7c52cfa29ab36bfefee +6847550886a1965deeac92950c2b29f13c48dde0ba5e84d4274cba0cf84f7e43
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.