All of lore.kernel.org
 help / color / mirror / Atom feed

diff for duplicates of <20150424191353.GA5293@cmpxchg.org>

diff --git a/a/1.txt b/N1/1.txt
index 65e5d7f..51cdd08 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -46,4 +46,10 @@ killing allocations still have the potential to deadlock.  Is there a
 reason we shouldn't just let them do an ALLOC_NO_WATERMARK allocation
 after the OOM victim exited (or timed out)?
 
-Otherwise, I'll just do that in the next iteration.
\ No newline at end of file
+Otherwise, I'll just do that in the next iteration.
+
+--
+To unsubscribe, send a message with 'unsubscribe linux-mm' in
+the body to majordomo@kvack.org.  For more info on Linux MM,
+see: http://www.linux-mm.org/ .
+Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
\ No newline at end of file
diff --git a/a/content_digest b/N1/content_digest
index fe26e5c..3e6ab5c 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -86,7 +86,13 @@
   "reason we shouldn't just let them do an ALLOC_NO_WATERMARK allocation\n",
   "after the OOM victim exited (or timed out)?\n",
   "\n",
-  "Otherwise, I'll just do that in the next iteration."
+  "Otherwise, I'll just do that in the next iteration.\n",
+  "\n",
+  "--\n",
+  "To unsubscribe, send a message with 'unsubscribe linux-mm' in\n",
+  "the body to majordomo\@kvack.org.  For more info on Linux MM,\n",
+  "see: http://www.linux-mm.org/ .\n",
+  "Don't email: <a href=mailto:\"dont\@kvack.org\"> email\@kvack.org </a>"
 ]
 
-a4d8b30f388aeed5252d045e4edab9ce943e25e517845617bc53a88af252cfa5
+f4351c1e32b705fdc6904280cea437252113fcb56d6fc6faa5e1f0f84d39d198
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.