diff for duplicates of <1459277829.6412.3.camel@intel.com> diff --git a/a/1.txt b/N1/1.txt index 90476c6..deb3bc2 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -10,3 +10,7 @@ Agreed - but how do we do this? clear_pmem needs to be able to clear an arbitrary number of bytes, but to go through the driver, we'd need to send down a bio? If only the driver had an rw_bytes like interface that could be used by anyone... :) +_______________________________________________ +Linux-nvdimm mailing list +Linux-nvdimm@lists.01.org +https://lists.01.org/mailman/listinfo/linux-nvdimm diff --git a/a/content_digest b/N1/content_digest index abdfd58..0f306ab 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -10,20 +10,19 @@ "Date\0Tue, 29 Mar 2016 18:57:16 +0000\0" "To\0Williams" " Dan J <dan.j.williams@intel.com>\0" - "Cc\0linux-block@vger.kernel.org <linux-block@vger.kernel.org>" + "Cc\0axboe@fb.com <axboe@fb.com>" + jack@suse.cz <jack@suse.cz> + linux-nvdimm@lists.01.org <linux-nvdimm@lists.01.org> + david@fromorbit.com <david@fromorbit.com> xfs@oss.sgi.com <xfs@oss.sgi.com> + linux-block@vger.kernel.org <linux-block@vger.kernel.org> linux-mm@kvack.org <linux-mm@kvack.org> viro@zeniv.linux.org.uk <viro@zeniv.linux.org.uk> - axboe@fb.com <axboe@fb.com> - akpm@linux-foundation.org <akpm@linux-foundation.org> - linux-nvdimm@lists.01.org <linux-nvdimm@lists.01.org> linux-fsdevel@vger.kernel.org <linux-fsdevel@vger.kernel.org> - ross.zwisler@linux.intel.com <ross.zwisler@linux.intel.com> + akpm@linux-foundation.org <akpm@linux-foundation.org> linux-ext4@vger.kernel.org <linux-ext4@vger.kernel.org> Wilcox - Matthew R <matthew.r.wilcox@intel.com> - david@fromorbit.com <david@fromorbit.com> - " jack@suse.cz <jack@suse.cz>\0" + "\0" "\00:1\0" "b\0" "On Mon, 2016-03-28 at 16:34 -0700, Dan Williams wrote:\n" @@ -37,6 +36,10 @@ "Agreed - but how do we do this? clear_pmem needs to be able to clear an\n" "arbitrary number of bytes, but to go through the driver, we'd need to\n" "send down a bio? If only the driver had an rw_bytes like interface that\n" - could be used by anyone... :) + "could be used by anyone... :)\n" + "_______________________________________________\n" + "Linux-nvdimm mailing list\n" + "Linux-nvdimm@lists.01.org\n" + https://lists.01.org/mailman/listinfo/linux-nvdimm -f58e2673d51fcdc75a3c7a2679d2d3af938c9043659e0952811eb86b09e1b880 +02d946fa388812ea29d619ac6034529ba7468082c739a34efad069796f78d726
diff --git a/a/1.txt b/N2/1.txt index 90476c6..35606e9 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -10,3 +10,7 @@ Agreed - but how do we do this? clear_pmem needs to be able to clear an arbitrary number of bytes, but to go through the driver, we'd need to send down a bio? If only the driver had an rw_bytes like interface that could be used by anyone... :) +_______________________________________________ +xfs mailing list +xfs@oss.sgi.com +http://oss.sgi.com/mailman/listinfo/xfs diff --git a/a/content_digest b/N2/content_digest index abdfd58..29707bc 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -10,20 +10,19 @@ "Date\0Tue, 29 Mar 2016 18:57:16 +0000\0" "To\0Williams" " Dan J <dan.j.williams@intel.com>\0" - "Cc\0linux-block@vger.kernel.org <linux-block@vger.kernel.org>" + "Cc\0axboe@fb.com <axboe@fb.com>" + jack@suse.cz <jack@suse.cz> + linux-nvdimm@lists.01.org <linux-nvdimm@lists.01.org> xfs@oss.sgi.com <xfs@oss.sgi.com> + linux-block@vger.kernel.org <linux-block@vger.kernel.org> linux-mm@kvack.org <linux-mm@kvack.org> viro@zeniv.linux.org.uk <viro@zeniv.linux.org.uk> - axboe@fb.com <axboe@fb.com> - akpm@linux-foundation.org <akpm@linux-foundation.org> - linux-nvdimm@lists.01.org <linux-nvdimm@lists.01.org> linux-fsdevel@vger.kernel.org <linux-fsdevel@vger.kernel.org> - ross.zwisler@linux.intel.com <ross.zwisler@linux.intel.com> + akpm@linux-foundation.org <akpm@linux-foundation.org> linux-ext4@vger.kernel.org <linux-ext4@vger.kernel.org> + ross.zwisler@linux.intel.com <ross.zwisler@linux.intel.com> Wilcox - Matthew R <matthew.r.wilcox@intel.com> - david@fromorbit.com <david@fromorbit.com> - " jack@suse.cz <jack@suse.cz>\0" + " Matthew R <matthew.r.wilcox@intel.com>\0" "\00:1\0" "b\0" "On Mon, 2016-03-28 at 16:34 -0700, Dan Williams wrote:\n" @@ -37,6 +36,10 @@ "Agreed - but how do we do this? clear_pmem needs to be able to clear an\n" "arbitrary number of bytes, but to go through the driver, we'd need to\n" "send down a bio? If only the driver had an rw_bytes like interface that\n" - could be used by anyone... :) + "could be used by anyone... :)\n" + "_______________________________________________\n" + "xfs mailing list\n" + "xfs@oss.sgi.com\n" + http://oss.sgi.com/mailman/listinfo/xfs -f58e2673d51fcdc75a3c7a2679d2d3af938c9043659e0952811eb86b09e1b880 +5506cfc8dabb98ef4c3113b87c4bfb5422a5b7468d1e415c1c9adc4a3bf5d0af
diff --git a/a/1.txt b/N3/1.txt index 90476c6..7a58c9f 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -3,10 +3,10 @@ On Mon, 2016-03-28 at 16:34 -0700, Dan Williams wrote: <> > Seems kind of sad to fail the fault due to a bad block when we were -> going to zero it anyway, right? I'm not seeing a compelling reason to +> going to zero it anyway, right?  I'm not seeing a compelling reason to > keep any zeroing in fs/dax.c. Agreed - but how do we do this? clear_pmem needs to be able to clear an arbitrary number of bytes, but to go through the driver, we'd need to send down a bio? If only the driver had an rw_bytes like interface that -could be used by anyone... :) +could be used by anyone... :)N‹§²æìr¸›zǧu©ž²Æ {\b†éì¹»\x1c®&Þ–)îÆi¢žØ^n‡r¶‰šŽŠÝ¢j$½§$¢¸\x05¢¹¨è§~Š'.)îÄÃ,yèm¶ŸÿÃ\f%Š{±šj+ƒðèž×¦j)Z†·Ÿ diff --git a/a/content_digest b/N3/content_digest index abdfd58..65a3f5e 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -31,12 +31,12 @@ "<>\n" "\n" "> Seems kind of sad to fail the fault due to a bad block when we were\n" - "> going to zero it anyway, right?\302\240\302\240I'm not seeing a compelling reason to\n" + "> going to zero it anyway, right?\303\202\302\240\303\202\302\240I'm not seeing a compelling reason to\n" "> keep any zeroing in fs/dax.c.\n" "\n" "Agreed - but how do we do this? clear_pmem needs to be able to clear an\n" "arbitrary number of bytes, but to go through the driver, we'd need to\n" "send down a bio? If only the driver had an rw_bytes like interface that\n" - could be used by anyone... :) + "could be used by anyone... :)N\302\213\302\247\302\262\303\246\303\254r\302\270\302\233z\303\207\302\247u\302\251\302\236\302\262\303\206\302\240{\b\302\255\302\206\303\251\303\254\302\271\302\273\034\302\256&\303\236\302\226)\303\256\303\206i\302\242\302\236\303\230^n\302\207r\302\266\302\211\302\232\302\216\302\212\303\235\302\242j$\302\275\302\247$\302\242\302\270\005\302\242\302\271\302\250\302\255\303\250\302\247~\302\212'.)\303\256\303\204\303\203,y\303\250m\302\266\302\237\303\277\303\203\f%\302\212{\302\261\302\232j+\302\203\303\260\303\250\302\236\303\227\302\246j)Z\302\206\302\267\302\237" -f58e2673d51fcdc75a3c7a2679d2d3af938c9043659e0952811eb86b09e1b880 +f7db86470eab94e1d827e5a2fd762001cc9e2cdc64bc5eebf2ec5a55250d1f42
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.