diff for duplicates of <87oa3pb6rd.fsf@kamboji.qca.qualcomm.com>

diff --git a/a/1.txt b/N1/1.txt
index 6cc9db1..ce923de 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -14,13 +14,15 @@ Ben Greear <greearb@candelatech.com> writes:
 >>>   drivers/net/wireless/ath/ath10k/wmi.c | 2 +-
 >>>   1 file changed, 1 insertion(+), 1 deletion(-)
 >>>
->>> diff --git a/drivers/net/wireless/ath/ath10k/wmi.c b/drivers/net/wireless/ath/ath10k/wmi.c
+>>> diff --git a/drivers/net/wireless/ath/ath10k/wmi.c b/drivers/net/wirele=
+ss/ath/ath10k/wmi.c
 >>> index 1758b4a..d9e4b77 100644
 >>> --- a/drivers/net/wireless/ath/ath10k/wmi.c
 >>> +++ b/drivers/net/wireless/ath/ath10k/wmi.c
->>> @@ -4050,7 +4050,7 @@ void ath10k_wmi_event_debug_print(struct ath10k *ar, struct sk_buff *skb)
+>>> @@ -4050,7 +4050,7 @@ void ath10k_wmi_event_debug_print(struct ath10k *=
+ar, struct sk_buff *skb)
 >>>   	/* the last byte is always reserved for the null character */
->>>   	buf[i] = '\0';
+>>>   	buf[i] =3D '\0';
 >>>
 >>> -	ath10k_dbg(ar, ATH10K_DBG_WMI_PRINT, "wmi print '%s'\n", buf);
 >>> +	ath10k_info(ar, "wmi print '%s'\n", buf);
@@ -30,12 +32,16 @@ Ben Greear <greearb@candelatech.com> writes:
 >> level for it. But I suspect that for normal users these are just
 >> confusing and unnecessarily spam the log.
 >
-> CT firmare will print out some memory usage info on firmware boot, and that can
-> allow a discerning individual to tune their vdev, peer, rate-ctrl, and other
+> CT firmare will print out some memory usage info on firmware boot, and th=
+at can
+> allow a discerning individual to tune their vdev, peer, rate-ctrl, and ot=
+her
 > object usage in order to make best use of resources in the firmware.
 >
-> These few lines can greatly aid debugging certain types of crashes and performance
-> loss in the firmware, so having them readily available in 'dmesg' or similar
+> These few lines can greatly aid debugging certain types of crashes and pe=
+rformance
+> loss in the firmware, so having them readily available in 'dmesg' or simi=
+lar
 > for bug reports from the field helps me.
 >
 > Stock firmware will also print out some resource usage info.  It is just
@@ -44,9 +50,5 @@ Ben Greear <greearb@candelatech.com> writes:
 I'm sure it's useful for you, but we have quite a few firmware versions
 to support. We do not know what kind of messages they print.
 
--- 
-Kalle Valo
-_______________________________________________
-ath10k mailing list
-ath10k@lists.infradead.org
-http://lists.infradead.org/mailman/listinfo/ath10k
+--=20
+Kalle Valo=
diff --git a/a/content_digest b/N1/content_digest
index 65cf5f5..94ab81f 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -26,13 +26,15 @@
  ">>>   drivers/net/wireless/ath/ath10k/wmi.c | 2 +-\n"
  ">>>   1 file changed, 1 insertion(+), 1 deletion(-)\n"
  ">>>\n"
- ">>> diff --git a/drivers/net/wireless/ath/ath10k/wmi.c b/drivers/net/wireless/ath/ath10k/wmi.c\n"
+ ">>> diff --git a/drivers/net/wireless/ath/ath10k/wmi.c b/drivers/net/wirele=\n"
+ "ss/ath/ath10k/wmi.c\n"
  ">>> index 1758b4a..d9e4b77 100644\n"
  ">>> --- a/drivers/net/wireless/ath/ath10k/wmi.c\n"
  ">>> +++ b/drivers/net/wireless/ath/ath10k/wmi.c\n"
- ">>> @@ -4050,7 +4050,7 @@ void ath10k_wmi_event_debug_print(struct ath10k *ar, struct sk_buff *skb)\n"
+ ">>> @@ -4050,7 +4050,7 @@ void ath10k_wmi_event_debug_print(struct ath10k *=\n"
+ "ar, struct sk_buff *skb)\n"
  ">>>   \t/* the last byte is always reserved for the null character */\n"
- ">>>   \tbuf[i] = '\\0';\n"
+ ">>>   \tbuf[i] =3D '\\0';\n"
  ">>>\n"
  ">>> -\tath10k_dbg(ar, ATH10K_DBG_WMI_PRINT, \"wmi print '%s'\\n\", buf);\n"
  ">>> +\tath10k_info(ar, \"wmi print '%s'\\n\", buf);\n"
@@ -42,12 +44,16 @@
  ">> level for it. But I suspect that for normal users these are just\n"
  ">> confusing and unnecessarily spam the log.\n"
  ">\n"
- "> CT firmare will print out some memory usage info on firmware boot, and that can\n"
- "> allow a discerning individual to tune their vdev, peer, rate-ctrl, and other\n"
+ "> CT firmare will print out some memory usage info on firmware boot, and th=\n"
+ "at can\n"
+ "> allow a discerning individual to tune their vdev, peer, rate-ctrl, and ot=\n"
+ "her\n"
  "> object usage in order to make best use of resources in the firmware.\n"
  ">\n"
- "> These few lines can greatly aid debugging certain types of crashes and performance\n"
- "> loss in the firmware, so having them readily available in 'dmesg' or similar\n"
+ "> These few lines can greatly aid debugging certain types of crashes and pe=\n"
+ "rformance\n"
+ "> loss in the firmware, so having them readily available in 'dmesg' or simi=\n"
+ "lar\n"
  "> for bug reports from the field helps me.\n"
  ">\n"
  "> Stock firmware will also print out some resource usage info.  It is just\n"
@@ -56,11 +62,7 @@
  "I'm sure it's useful for you, but we have quite a few firmware versions\n"
  "to support. We do not know what kind of messages they print.\n"
  "\n"
- "-- \n"
- "Kalle Valo\n"
- "_______________________________________________\n"
- "ath10k mailing list\n"
- "ath10k@lists.infradead.org\n"
- http://lists.infradead.org/mailman/listinfo/ath10k
+ "--=20\n"
+ Kalle Valo=
 
-869e872ecbafb3ebdcb7204b8d0f3ae25d25e6d07470d012c0163b5baf80e79f
+b106a27267424861276b45629c211c63398b3d04736d87e16f3f71500d7def75
