All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20170609140853.GA14760@cmpxchg.org>

diff --git a/a/1.txt b/N1/1.txt
index 3ff9523..437cafc 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -47,9 +47,3 @@ I'm not a fan of defensive programming, but is this call to OOM more
 expensive than the printk() somehow? And how certain are you that no
 VM_FAULT_OOMs will leak, given how spread out page fault handlers and
 how complex the different allocation contexts inside them are?
-
---
-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>
diff --git a/a/content_digest b/N1/content_digest
index 8c602cc..c43d89a 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -61,12 +61,6 @@
  "I'm not a fan of defensive programming, but is this call to OOM more\n"
  "expensive than the printk() somehow? And how certain are you that no\n"
  "VM_FAULT_OOMs will leak, given how spread out page fault handlers and\n"
- "how complex the different allocation contexts inside them are?\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>"
+ how complex the different allocation contexts inside them are?
 
-4bb79e53f8d516e7f505f580c0c0f751dea1840f5d9417317ce255cf96aa5fcc
+7089c5661490c87a01b7cfc3f7460d3895d5ecb91202ae86d2011698d8fc8fae

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.