All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <50FD6003.8060703@parallels.com>

diff --git a/a/1.txt b/N1/1.txt
index e3b97cc..bf7362b 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -72,3 +72,11 @@ extra lock (and we'll never be able to stop holding the creation lock,
 whatever it is). So my main point here is not memcg_mutex vs
 set_limit_mutex, but rather, memcg_mutex is needed anyway, and once it
 is taken, the set_limit_mutex *can* be held, but doesn't need to.
+
+
+
+--
+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 0633ead..31e9a2f 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -3,16 +3,15 @@
  "ref\020130121144919.GO7798@dhcp22.suse.cz\0"
  "ref\050FD5AC0.9020406@parallels.com\0"
  "ref\020130121152032.GP7798@dhcp22.suse.cz\0"
- "ref\020130121152032.GP7798-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org\0"
- "From\0Glauber Costa <glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>\0"
+ "From\0Glauber Costa <glommer@parallels.com>\0"
  "Subject\0Re: [PATCH v3 4/6] memcg: replace cgroup_lock with memcg specific memcg_lock\0"
  "Date\0Mon, 21 Jan 2013 19:34:27 +0400\0"
- "To\0Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>\0"
- "Cc\0cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
-  linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org
-  Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
-  Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
- " kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org\0"
+ "To\0Michal Hocko <mhocko@suse.cz>\0"
+ "Cc\0cgroups@vger.kernel.org"
+  linux-mm@kvack.org
+  Tejun Heo <tj@kernel.org>
+  Johannes Weiner <hannes@cmpxchg.org>
+ " kamezawa.hiroyu@jp.fujitsu.com\0"
  "\00:1\0"
  "b\0"
  "On 01/21/2013 07:20 PM, Michal Hocko wrote:\n"
@@ -88,6 +87,14 @@
  "extra lock (and we'll never be able to stop holding the creation lock,\n"
  "whatever it is). So my main point here is not memcg_mutex vs\n"
  "set_limit_mutex, but rather, memcg_mutex is needed anyway, and once it\n"
- is taken, the set_limit_mutex *can* be held, but doesn't need to.
+ "is taken, the set_limit_mutex *can* be held, but doesn't need to.\n"
+ "\n"
+ "\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>"
 
-136f6e2ba3768ed0f5232d076d9874a4aeac5e9a5bb7da579f6860525ed83161
+922783942fa1aeab5faf1f9a51ffe176a6d3e91ccc139db83baf2d760ddfb5b1

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.