All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <53338CFE.3060705@huawei.com>

diff --git a/a/1.txt b/N1/1.txt
index 9f2e0d9..893c237 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -22,7 +22,7 @@ On 2014/3/22 7:37, Catalin Marinas wrote:
 >>    by Catalin.
 > 
 > I think there was a slight misunderstanding. My point was about "echo
-> scan=off!+- before !?echo off!+-, they can just be squashed into the
+> scan=off” before “echo off”, they can just be squashed into the
 > same action of the latter.
 > 
 
@@ -30,13 +30,7 @@ I'm not sure if I understand correctly, so you want the "off" handler to
 stop the scan thread but it will never free kmemleak objects until the 
 user explicitly trigger the "clear" action, right?
 
-> I would keep the !?clear!+- part separately as per your first patch. I
+> I would keep the “clear” part separately as per your first patch. I
 > recall people asked in the past to still be able to analyse the reports
 > even though kmemleak failed or was disabled.
-> 
-
---
-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 ffe7a76..fd89f29 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -33,7 +33,7 @@
  ">>    by Catalin.\n"
  "> \n"
  "> I think there was a slight misunderstanding. My point was about \"echo\n"
- "> scan=off!+- before !?echo off!+-, they can just be squashed into the\n"
+ "> scan=off\342\200\235 before \342\200\234echo off\342\200\235, they can just be squashed into the\n"
  "> same action of the latter.\n"
  "> \n"
  "\n"
@@ -41,15 +41,9 @@
  "stop the scan thread but it will never free kmemleak objects until the \n"
  "user explicitly trigger the \"clear\" action, right?\n"
  "\n"
- "> I would keep the !?clear!+- part separately as per your first patch. I\n"
+ "> I would keep the \342\200\234clear\342\200\235 part separately as per your first patch. I\n"
  "> recall people asked in the past to still be able to analyse the reports\n"
  "> even though kmemleak failed or was disabled.\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>"
+ >
 
-4178137e495ac0221a019f0dd915f24693b4d34210e1f720e27aba8696152790
+c9f84450da4c4277d1a0495180ee255a2df309239a40fe0677f83c2552d9ad69

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.