diff for duplicates of <20220505055817.GQ4031@kadam>
diff --git a/a/1.txt b/N1/1.txt
index 4998f39..7f6008a 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -26,4 +26,10 @@ Link: https://lore.kernel.org/r/1644308006-22784-5-git-send-email-quic_cjhuang@q
the original commit and include links to those threads?
regards,
-dan carpenter
\ No newline at end of file
+dan carpenter
+
+
+--
+ath11k mailing list
+ath11k@lists.infradead.org
+http://lists.infradead.org/mailman/listinfo/ath11k
\ No newline at end of file
diff --git a/a/content_digest b/N1/content_digest
index d2070de..060bfb1 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -63,7 +63,13 @@
"the original commit and include links to those threads?\n",
"\n",
"regards,\n",
- "dan carpenter"
+ "dan carpenter\n",
+ "\n",
+ "\n",
+ "-- \n",
+ "ath11k mailing list\n",
+ "ath11k\@lists.infradead.org\n",
+ "http://lists.infradead.org/mailman/listinfo/ath11k"
]
-fe2301723981fdb4cd764eaa3a7f7e3af6f9ad919ab987e4672f37ea60982dbc
+1de70b60ee25938845a0d582c137df62016a312cc783558f5940a380b3a315af
diff --git a/a/1.txt b/N2/1.txt
index 4998f39..7118994 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -20,7 +20,7 @@ lore.kernel.org so we could have used that as an In-Reply-to tag.
In an ideal world, all the bug reports for a patch would go to a
standard location.
-Link: https://lore.kernel.org/r/1644308006-22784-5-git-send-email-quic_cjhuang@quicinc.com
+Link: https://lore.kernel.org/r/1644308006-22784-5-git-send-email-quic_cjhuang(a)quicinc.com
3) Another idea is that the kbuild bot could search lore for Fixes to
the original commit and include links to those threads?
diff --git a/a/content_digest b/N2/content_digest
index d2070de..d122661 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -1,9 +1,3 @@
-[
- "ref\000202205032236.kofEquX3-lkp\@intel.com\0"
-]
-[
- "ref\0o5hh7658dxr.fsf\@quicinc.com\0"
-]
[
"ref\0fd76aa54-4d05-a4b0-b3b4-11c8a5be799c\@quicinc.com\0"
]
@@ -14,22 +8,13 @@
"Subject\0Re: [linux-next:master 408/8237] drivers/net/wireless/ath/ath11k/wow.c:712 ath11k_wow_op_resume() warn: inconsistent returns '&ar->conf_mutex'.\0"
]
[
- "Date\0Thu, 5 May 2022 08:58:17 +0300\0"
-]
-[
- "To\0Carl Huang <quic_cjhuang\@quicinc.com>",
- " lkp\@intel.com\0"
+ "Date\0Thu, 05 May 2022 08:58:17 +0300\0"
]
[
- "Cc\0Kalle Valo <quic_kvalo\@quicinc.com>",
- " kbuild\@lists.01.org",
- " kbuild-all\@lists.01.org",
- " Linux Memory Management List <linux-mm\@kvack.org>",
- " ath11k\@lists.infradead.org",
- " Wen Gong <quic_wgong\@quicinc.com>\0"
+ "To\0kbuild\@lists.01.org\0"
]
[
- "\0000:1\0"
+ "\0001:1\0"
]
[
"b\0"
@@ -57,7 +42,7 @@
"In an ideal world, all the bug reports for a patch would go to a\n",
"standard location.\n",
"\n",
- "Link: https://lore.kernel.org/r/1644308006-22784-5-git-send-email-quic_cjhuang\@quicinc.com\n",
+ "Link: https://lore.kernel.org/r/1644308006-22784-5-git-send-email-quic_cjhuang(a)quicinc.com\n",
"\n",
"3) Another idea is that the kbuild bot could search lore for Fixes to\n",
"the original commit and include links to those threads?\n",
@@ -66,4 +51,4 @@
"dan carpenter"
]
-fe2301723981fdb4cd764eaa3a7f7e3af6f9ad919ab987e4672f37ea60982dbc
+80369df5816b71ab5f786d71eca2a60645eb68eb5fb858162e82be611587ff0c
diff --git a/a/1.txt b/N3/1.txt
index 4998f39..7118994 100644
--- a/a/1.txt
+++ b/N3/1.txt
@@ -20,7 +20,7 @@ lore.kernel.org so we could have used that as an In-Reply-to tag.
In an ideal world, all the bug reports for a patch would go to a
standard location.
-Link: https://lore.kernel.org/r/1644308006-22784-5-git-send-email-quic_cjhuang@quicinc.com
+Link: https://lore.kernel.org/r/1644308006-22784-5-git-send-email-quic_cjhuang(a)quicinc.com
3) Another idea is that the kbuild bot could search lore for Fixes to
the original commit and include links to those threads?
diff --git a/a/content_digest b/N3/content_digest
index d2070de..1cc2042 100644
--- a/a/content_digest
+++ b/N3/content_digest
@@ -1,9 +1,3 @@
-[
- "ref\000202205032236.kofEquX3-lkp\@intel.com\0"
-]
-[
- "ref\0o5hh7658dxr.fsf\@quicinc.com\0"
-]
[
"ref\0fd76aa54-4d05-a4b0-b3b4-11c8a5be799c\@quicinc.com\0"
]
@@ -14,22 +8,13 @@
"Subject\0Re: [linux-next:master 408/8237] drivers/net/wireless/ath/ath11k/wow.c:712 ath11k_wow_op_resume() warn: inconsistent returns '&ar->conf_mutex'.\0"
]
[
- "Date\0Thu, 5 May 2022 08:58:17 +0300\0"
-]
-[
- "To\0Carl Huang <quic_cjhuang\@quicinc.com>",
- " lkp\@intel.com\0"
+ "Date\0Thu, 05 May 2022 08:58:17 +0300\0"
]
[
- "Cc\0Kalle Valo <quic_kvalo\@quicinc.com>",
- " kbuild\@lists.01.org",
- " kbuild-all\@lists.01.org",
- " Linux Memory Management List <linux-mm\@kvack.org>",
- " ath11k\@lists.infradead.org",
- " Wen Gong <quic_wgong\@quicinc.com>\0"
+ "To\0kbuild-all\@lists.01.org\0"
]
[
- "\0000:1\0"
+ "\0001:1\0"
]
[
"b\0"
@@ -57,7 +42,7 @@
"In an ideal world, all the bug reports for a patch would go to a\n",
"standard location.\n",
"\n",
- "Link: https://lore.kernel.org/r/1644308006-22784-5-git-send-email-quic_cjhuang\@quicinc.com\n",
+ "Link: https://lore.kernel.org/r/1644308006-22784-5-git-send-email-quic_cjhuang(a)quicinc.com\n",
"\n",
"3) Another idea is that the kbuild bot could search lore for Fixes to\n",
"the original commit and include links to those threads?\n",
@@ -66,4 +51,4 @@
"dan carpenter"
]
-fe2301723981fdb4cd764eaa3a7f7e3af6f9ad919ab987e4672f37ea60982dbc
+bd8f13f6a423e46d965b9b4f48edd297274449b618c2602405f0addee596278d
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.