diff for duplicates of <4dfb0d6a-aa48-4d96-82f0-09a960b1012f@linux.dev>

diff --git a/a/1.txt b/N1/1.txt
index ff41fa3..13ec807 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -20,3 +20,8 @@ You are right. The
    {.opcode = BPF_ALU64 | BPF_MOVSX | BPF_K, .offset = 32, .imm = -1}
 is not supported by bpf ISA. Currently, it will be an illegal encoding
 from kernel perspective.
+
+-- 
+Bpf mailing list
+Bpf@ietf.org
+https://www.ietf.org/mailman/listinfo/bpf
diff --git a/a/content_digest b/N1/content_digest
index 7f99077..71cc1ef 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -3,7 +3,7 @@
  "ref\0829aa552-b04e-4f08-9874-b3f929741852@linux.dev\0"
  "ref\0095f01da48e8$611687d0$23439770$@gmail.com\0"
  "From\0Yonghong Song <yonghong.song@linux.dev>\0"
- "Subject\0Re: Sign extension ISA question\0"
+ "Subject\0Re: [Bpf] Sign extension ISA question\0"
  "Date\0Tue, 16 Jan 2024 19:48:44 -0800\0"
  "To\0dthaler1968@googlemail.com\0"
  "Cc\0bpf@ietf.org"
@@ -31,6 +31,11 @@
  "You are right. The\n"
  "   {.opcode = BPF_ALU64 | BPF_MOVSX | BPF_K, .offset = 32, .imm = -1}\n"
  "is not supported by bpf ISA. Currently, it will be an illegal encoding\n"
- from kernel perspective.
+ "from kernel perspective.\n"
+ "\n"
+ "-- \n"
+ "Bpf mailing list\n"
+ "Bpf@ietf.org\n"
+ https://www.ietf.org/mailman/listinfo/bpf
 
-fa6d3116e3e6d0b8fc8cc7bed42d86b7bcb7945586b7a4b1af0c311fd75b087b
+14a1872b9811856da134fb8cbbdad8acadaae7ba4364246ab3736bd88ba17261
