diff for duplicates of <CAPcyv4jN7ntOO2hK4ByDcX4-Kob=aJNOr3fGR_k_8rxZ=3Sz7w@mail.gmail.com>
diff --git a/a/1.txt b/N1/1.txt
index 6705ef8..0d8de25 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -170,7 +170,4 @@ I think you're right. The path I'm concerned about not regressing is
the error clearing on new block allocation and we get that already via
xfs_zero_extent() and sb_issue_zeroout(). For your fs we'll want a
dax-device equivalent for that path, but that does mean that
-__dax_zero_page_range() stays out of the error clearing game.
-_______________________________________________
-Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
-To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
\ No newline at end of file
+__dax_zero_page_range() stays out of the error clearing game.
\ No newline at end of file
diff --git a/a/content_digest b/N1/content_digest
index ab9addb..ffadca8 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -45,6 +45,7 @@
]
[
"Cc\0Dave Chinner <david\@fromorbit.com>",
+ " Jeff Moyer <jmoyer\@redhat.com>",
" linux-fsdevel <linux-fsdevel\@vger.kernel.org>",
" linux-nvdimm <linux-nvdimm\@lists.01.org>",
" Christoph Hellwig <hch\@infradead.org>",
@@ -229,10 +230,7 @@
"the error clearing on new block allocation and we get that already via\n",
"xfs_zero_extent() and sb_issue_zeroout(). For your fs we'll want a\n",
"dax-device equivalent for that path, but that does mean that\n",
- "__dax_zero_page_range() stays out of the error clearing game.\n",
- "_______________________________________________\n",
- "Linux-nvdimm mailing list -- linux-nvdimm\@lists.01.org\n",
- "To unsubscribe send an email to linux-nvdimm-leave\@lists.01.org"
+ "__dax_zero_page_range() stays out of the error clearing game."
]
-5d843f4ad570b6ffd87ef676d5fa8768762ceeb2061224bbf34f3670b274c231
+a2c27fd454e372b793e121c05f4bb086898a17fa7ad6db04eab903a3920514a7
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.