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

diff --git a/a/1.txt b/N1/1.txt
index 83f0ba3..40cbd2b 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -13,12 +13,13 @@ Adrian Chadd <adrian@freebsd.org> writes:
 
 > --- a/drivers/net/wireless/ath/ath10k/core.c
 > +++ b/drivers/net/wireless/ath/ath10k/core.c
-> @@ -2444,6 +2444,8 @@ struct ath10k *ath10k_core_create(size_t priv_size, struct device *dev,
->  	ar->hw_rev = hw_rev;
->  	ar->hif.ops = hif_ops;
->  	ar->hif.bus = bus;
-> +	ar->debug_mask = ath10k_debug_mask;
-> +	ar->trace_debug_mask = ath10k_debug_mask;
+> @@ -2444,6 +2444,8 @@ struct ath10k *ath10k_core_create(size_t priv_size,=
+ struct device *dev,
+>  	ar->hw_rev =3D hw_rev;
+>  	ar->hif.ops =3D hif_ops;
+>  	ar->hif.bus =3D bus;
+> +	ar->debug_mask =3D ath10k_debug_mask;
+> +	ar->trace_debug_mask =3D ath10k_debug_mask;
 
 Until now tracing has been always enabled, irrespective what debug_mask
 has contained. Now you are changing that and by default log messages are
@@ -30,9 +31,5 @@ the debugfs file.
 But is it really needed to be able to filter trace messages? debug_mask
 I understand, but not sure about trace_debug_mask.
 
--- 
-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 d804f62..6839f91 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -3,8 +3,8 @@
  "Subject\0Re: [PATCH] ath10k: add configurable debugging.\0"
  "Date\0Wed, 31 May 2017 12:16:44 +0000\0"
  "To\0Adrian Chadd <adrian@freebsd.org>\0"
- "Cc\0linux-wireless@vger.kernel.org <linux-wireless@vger.kernel.org>"
- " ath10k@lists.infradead.org <ath10k@lists.infradead.org>\0"
+ "Cc\0ath10k@lists.infradead.org <ath10k@lists.infradead.org>"
+ " linux-wireless@vger.kernel.org <linux-wireless@vger.kernel.org>\0"
  "\00:1\0"
  "b\0"
  "Adrian Chadd <adrian@freebsd.org> writes:\n"
@@ -22,12 +22,13 @@
  "\n"
  "> --- a/drivers/net/wireless/ath/ath10k/core.c\n"
  "> +++ b/drivers/net/wireless/ath/ath10k/core.c\n"
- "> @@ -2444,6 +2444,8 @@ struct ath10k *ath10k_core_create(size_t priv_size, struct device *dev,\n"
- ">  \tar->hw_rev = hw_rev;\n"
- ">  \tar->hif.ops = hif_ops;\n"
- ">  \tar->hif.bus = bus;\n"
- "> +\tar->debug_mask = ath10k_debug_mask;\n"
- "> +\tar->trace_debug_mask = ath10k_debug_mask;\n"
+ "> @@ -2444,6 +2444,8 @@ struct ath10k *ath10k_core_create(size_t priv_size,=\n"
+ " struct device *dev,\n"
+ ">  \tar->hw_rev =3D hw_rev;\n"
+ ">  \tar->hif.ops =3D hif_ops;\n"
+ ">  \tar->hif.bus =3D bus;\n"
+ "> +\tar->debug_mask =3D ath10k_debug_mask;\n"
+ "> +\tar->trace_debug_mask =3D ath10k_debug_mask;\n"
  "\n"
  "Until now tracing has been always enabled, irrespective what debug_mask\n"
  "has contained. Now you are changing that and by default log messages are\n"
@@ -39,11 +40,7 @@
  "But is it really needed to be able to filter trace messages? debug_mask\n"
  "I understand, but not sure about trace_debug_mask.\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=
 
-d3283d7ee797467ac83402d542e19c5ee4c69ec45d3a41b0c800d0ec27f80c9a
+416ce6fbdfecc34b4bce620c31da91bdad9da1cd945d1df9d38175c946fd3781
