All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20191226224802.GR4203@ZenIV.linux.org.uk>

diff --git a/a/1.txt b/N1/1.txt
index aa2ca6f..e0a93ed 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -20,7 +20,3 @@ It's a good catch; even if there is a reason why we never
 hit the blocking allocation in there, that reason should be
 spelled out in the code.  It isn't, and that can easily
 grow into a bug even if it hasn't done so already.
-
-______________________________________________________
-Linux MTD discussion mailing list
-http://lists.infradead.org/mailman/listinfo/linux-mtd/
diff --git a/a/content_digest b/N1/content_digest
index 5e9e9b7..7dd529e 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -3,10 +3,10 @@
  "Subject\0Re: [PATCH] fs: jffs2: fix possible sleep-in-atomic-context bugs\0"
  "Date\0Thu, 26 Dec 2019 22:48:02 +0000\0"
  "To\0Jia-Ju Bai <baijiaju1990@gmail.com>\0"
- "Cc\0richard@nod.at"
-  dwmw2@infradead.org
-  linux-kernel@vger.kernel.org
- " linux-mtd@lists.infradead.org\0"
+ "Cc\0dwmw2@infradead.org"
+  richard@nod.at
+  linux-mtd@lists.infradead.org
+ " linux-kernel@vger.kernel.org\0"
  "\00:1\0"
  "b\0"
  "On Tue, Dec 17, 2019 at 09:51:43PM +0800, Jia-Ju Bai wrote:\n"
@@ -30,10 +30,6 @@
  "It's a good catch; even if there is a reason why we never\n"
  "hit the blocking allocation in there, that reason should be\n"
  "spelled out in the code.  It isn't, and that can easily\n"
- "grow into a bug even if it hasn't done so already.\n"
- "\n"
- "______________________________________________________\n"
- "Linux MTD discussion mailing list\n"
- http://lists.infradead.org/mailman/listinfo/linux-mtd/
+ grow into a bug even if it hasn't done so already.
 
-a7f2476c0992fb095715f784a8dbf04ee9ab8d23b309135e88ed903a77b11a71
+3d22316e0b807d8270a04a5cd5e1165b3a2cde98da7a8e2af2335692dcb0b554

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.