All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20171229162250.7d68a0c8@archlinux>

diff --git a/a/1.txt b/N1/1.txt
index df8f5ff..38afa7a 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,12 +1,12 @@
 On Fri, 22 Dec 2017 17:07:17 +0200
-Eugen Hristev <eugen.hristev-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org> wrote:
+Eugen Hristev <eugen.hristev@microchip.com> wrote:
 
 > On module remove, if we do not call trigger remove, the trigger
 > stays in the subsystem, and on further module insert, we will have
 > multiple triggers, and the old one is not usable.
 > Have to call the remove function on module remove to solve this.
 > 
-> Signed-off-by: Eugen Hristev <eugen.hristev-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>
+> Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
 
 This needs more explanation.  I can't see why the managed removal
 isn't sufficient.  On removal the dev should have gone away taking
diff --git a/a/content_digest b/N1/content_digest
index 8a3f15f..784fe22 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,30 +1,29 @@
  "ref\01513955241-10985-1-git-send-email-eugen.hristev@microchip.com\0"
  "ref\01513955241-10985-11-git-send-email-eugen.hristev@microchip.com\0"
- "ref\01513955241-10985-11-git-send-email-eugen.hristev-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org\0"
- "From\0Jonathan Cameron <jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>\0"
+ "From\0Jonathan Cameron <jic23@kernel.org>\0"
  "Subject\0Re: [PATCH 10/14] iio: adc: at91-sama5d2_adc: force trigger removal on module remove\0"
  "Date\0Fri, 29 Dec 2017 16:22:50 +0000\0"
- "To\0Eugen Hristev <eugen.hristev-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>\0"
- "Cc\0nicolas.ferre-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org"
-  ludovic.desroches-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org
-  alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org
-  linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-  linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
-  devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-  linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-  linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
- " dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org\0"
+ "To\0Eugen Hristev <eugen.hristev@microchip.com>\0"
+ "Cc\0<nicolas.ferre@microchip.com>"
+  <ludovic.desroches@microchip.com>
+  <alexandre.belloni@free-electrons.com>
+  <linux-iio@vger.kernel.org>
+  <linux-arm-kernel@lists.infradead.org>
+  <devicetree@vger.kernel.org>
+  <linux-kernel@vger.kernel.org>
+  <linux-input@vger.kernel.org>
+ " <dmitry.torokhov@gmail.com>\0"
  "\00:1\0"
  "b\0"
  "On Fri, 22 Dec 2017 17:07:17 +0200\n"
- "Eugen Hristev <eugen.hristev-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org> wrote:\n"
+ "Eugen Hristev <eugen.hristev@microchip.com> wrote:\n"
  "\n"
  "> On module remove, if we do not call trigger remove, the trigger\n"
  "> stays in the subsystem, and on further module insert, we will have\n"
  "> multiple triggers, and the old one is not usable.\n"
  "> Have to call the remove function on module remove to solve this.\n"
  "> \n"
- "> Signed-off-by: Eugen Hristev <eugen.hristev-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>\n"
+ "> Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>\n"
  "\n"
  "This needs more explanation.  I can't see why the managed removal\n"
  "isn't sufficient.  On removal the dev should have gone away taking\n"
@@ -53,4 +52,4 @@
  ">  \n"
  ">  \tat91_adc_dma_disable(pdev);"
 
-0dfc4cab0f41f757d47211820269f899e56e46061468d6f6ca0334a9437abff8
+5a49a007fef5f52e8b5adc956a66995fdd101499e6eb676b82253ceee35d02e2

diff --git a/a/1.txt b/N2/1.txt
index df8f5ff..38afa7a 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -1,12 +1,12 @@
 On Fri, 22 Dec 2017 17:07:17 +0200
-Eugen Hristev <eugen.hristev-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org> wrote:
+Eugen Hristev <eugen.hristev@microchip.com> wrote:
 
 > On module remove, if we do not call trigger remove, the trigger
 > stays in the subsystem, and on further module insert, we will have
 > multiple triggers, and the old one is not usable.
 > Have to call the remove function on module remove to solve this.
 > 
-> Signed-off-by: Eugen Hristev <eugen.hristev-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>
+> Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
 
 This needs more explanation.  I can't see why the managed removal
 isn't sufficient.  On removal the dev should have gone away taking
diff --git a/a/content_digest b/N2/content_digest
index 8a3f15f..69caa45 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -1,30 +1,20 @@
  "ref\01513955241-10985-1-git-send-email-eugen.hristev@microchip.com\0"
  "ref\01513955241-10985-11-git-send-email-eugen.hristev@microchip.com\0"
- "ref\01513955241-10985-11-git-send-email-eugen.hristev-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org\0"
- "From\0Jonathan Cameron <jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>\0"
- "Subject\0Re: [PATCH 10/14] iio: adc: at91-sama5d2_adc: force trigger removal on module remove\0"
+ "From\0jic23@kernel.org (Jonathan Cameron)\0"
+ "Subject\0[PATCH 10/14] iio: adc: at91-sama5d2_adc: force trigger removal on module remove\0"
  "Date\0Fri, 29 Dec 2017 16:22:50 +0000\0"
- "To\0Eugen Hristev <eugen.hristev-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>\0"
- "Cc\0nicolas.ferre-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org"
-  ludovic.desroches-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org
-  alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org
-  linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-  linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
-  devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-  linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-  linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
- " dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "On Fri, 22 Dec 2017 17:07:17 +0200\n"
- "Eugen Hristev <eugen.hristev-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org> wrote:\n"
+ "Eugen Hristev <eugen.hristev@microchip.com> wrote:\n"
  "\n"
  "> On module remove, if we do not call trigger remove, the trigger\n"
  "> stays in the subsystem, and on further module insert, we will have\n"
  "> multiple triggers, and the old one is not usable.\n"
  "> Have to call the remove function on module remove to solve this.\n"
  "> \n"
- "> Signed-off-by: Eugen Hristev <eugen.hristev-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>\n"
+ "> Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>\n"
  "\n"
  "This needs more explanation.  I can't see why the managed removal\n"
  "isn't sufficient.  On removal the dev should have gone away taking\n"
@@ -53,4 +43,4 @@
  ">  \n"
  ">  \tat91_adc_dma_disable(pdev);"
 
-0dfc4cab0f41f757d47211820269f899e56e46061468d6f6ca0334a9437abff8
+ab7cfa2718c387c1fdccb0564051015de5fc9782842d95e1c7da8a12d82ca7b5

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.