All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <000000000000f020a905f061d4c2@google.com>

diff --git a/a/1.txt b/N1/1.txt
index 834cac3..660cd57 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -93,9 +93,3 @@ syzbot will keep track of this issue. See:
 https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
 syzbot can test patches for this issue, for details see:
 https://goo.gl/tpsmEJ#testing-patches
-
-
-_______________________________________________
-Linux-f2fs-devel mailing list
-Linux-f2fs-devel@lists.sourceforge.net
-https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
diff --git a/a/content_digest b/N1/content_digest
index 4e57fbb..61b5396 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,5 +1,5 @@
  "From\0syzbot <syzbot+e1246909d526a9d470fa@syzkaller.appspotmail.com>\0"
- "Subject\0[f2fs-dev] [syzbot] [f2fs?] [tmpfs?] kernel BUG in f2fs_evict_inode\0"
+ "Subject\0[syzbot] [f2fs?] [tmpfs?] kernel BUG in f2fs_evict_inode\0"
  "Date\0Wed, 21 Dec 2022 18:57:38 -0800\0"
  "To\0akpm@linux-foundation.org"
   chao@kernel.org
@@ -105,12 +105,6 @@
  "syzbot will keep track of this issue. See:\n"
  "https://goo.gl/tpsmEJ#status for how to communicate with syzbot.\n"
  "syzbot can test patches for this issue, for details see:\n"
- "https://goo.gl/tpsmEJ#testing-patches\n"
- "\n"
- "\n"
- "_______________________________________________\n"
- "Linux-f2fs-devel mailing list\n"
- "Linux-f2fs-devel@lists.sourceforge.net\n"
- https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
+ https://goo.gl/tpsmEJ#testing-patches
 
-21fb988a586b38e534e7cf6215c9f6cb7afbf4786f593b29e9c680b255022db6
+45622ae5e989b201e17357b4ed5ad9415d5342dd196517bf7d535f20a4284b9a

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.