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

diff --git a/a/1.txt b/N1/1.txt
index 440040e..f0a47fb 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -15,8 +15,3 @@ In the iomap_ops structure passed to iomap_fiemap.
 The iomap_begin callback is where you do the mapping.  the iomap_end
 callback does any required cleanup, which in case of GFS2 probably
 would be dropping the cluster lock protecting the mapping.
-
-_______________________________________________
-xfs mailing list
-xfs@oss.sgi.com
-http://oss.sgi.com/mailman/listinfo/xfs
diff --git a/a/content_digest b/N1/content_digest
index 63201e9..e282cd1 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -5,10 +5,10 @@
  "Subject\0Re: [PATCH 09/15] fs: iomap based fiemap implementation\0"
  "Date\0Tue, 24 May 2016 15:10:58 +0200\0"
  "To\0Bob Peterson <rpeterso@redhat.com>\0"
- "Cc\0linux-fsdevel@vger.kernel.org"
+ "Cc\0Christoph Hellwig <hch@lst.de>"
+  xfs@oss.sgi.com
   vishal l verma <vishal.l.verma@intel.com>
-  Christoph Hellwig <hch@lst.de>
- " xfs@oss.sgi.com\0"
+ " linux-fsdevel@vger.kernel.org\0"
  "\00:1\0"
  "b\0"
  "On Mon, May 23, 2016 at 04:09:26PM -0400, Bob Peterson wrote:\n"
@@ -27,11 +27,6 @@
  "\n"
  "The iomap_begin callback is where you do the mapping.  the iomap_end\n"
  "callback does any required cleanup, which in case of GFS2 probably\n"
- "would be dropping the cluster lock protecting the mapping.\n"
- "\n"
- "_______________________________________________\n"
- "xfs mailing list\n"
- "xfs@oss.sgi.com\n"
- http://oss.sgi.com/mailman/listinfo/xfs
+ would be dropping the cluster lock protecting the mapping.
 
-39ee93f76cbda9870c586f3cd1caac866287bb959916dfe81fc84323f843ce7d
+82695766e4251205df6f00e2edeeb34da14aef13f067fc49fd85eab844c38f6d

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.