All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20161119042224.GA25063@localhost.localdomain>

diff --git a/a/1.txt b/N1/1.txt
index bfe276f..4eea7dc 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -4,7 +4,7 @@ Thanks for your patience to take the time to explain to me how the
 firmware/linux split is done in your platform. Still, one thing is not
 clear to me.
 
-On Fri, Nov 18, 2016 at 09:32:47AM +0100, kernel-TqfNSX0MhmxHKSADF0wUEw@public.gmane.org wrote:
+On Fri, Nov 18, 2016 at 09:32:47AM +0100, kernel at martin.sperl.org wrote:
 > 
 
 > The way that firmware works on the RPI is quite different from most others I guess.
@@ -47,7 +47,7 @@ boot? How about module insertion?
 
 Who has the ownership of this device?
 
-> The above mentioned “configuration if not running” reflect the values that
+> The above mentioned ?configuration if not running? reflect the values that
 > the FW is currently setting. We should not change those values as long as the
 > Firmware is also reading the temperature on its own.
 
@@ -77,7 +77,7 @@ initialized?
 > > it is clear to whoever reads in the future), then I would be OK with
 > > this driver. 
 > 
-> So how do you want this to get “documented” in the driver?
+> So how do you want this to get ?documented? in the driver?
 > The setup and Firmware is a generic feature of the SOC, so if we would put
 > some clarifications in this driver, then we would need to put it in every
 > bcm283X driver (which seems unreasonable).
@@ -94,7 +94,3 @@ accessing this device.
 
 > Thanks,
 > 	Martin
---
-To unsubscribe from this list: send the line "unsubscribe devicetree" in
-the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff --git a/a/content_digest b/N1/content_digest
index 8b298bf..46b7d37 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -4,26 +4,10 @@
  "ref\0766e1b70-d83a-eb52-fa2b-aec435e85673@martin.sperl.org\0"
  "ref\020161117151019.GA3115@localhost.localdomain\0"
  "ref\07957B3CC-0E18-4B27-82EB-EF88B7695E28@martin.sperl.org\0"
- "ref\07957B3CC-0E18-4B27-82EB-EF88B7695E28-TqfNSX0MhmxHKSADF0wUEw@public.gmane.org\0"
- "From\0Eduardo Valentin <edubezval-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>\0"
- "Subject\0Re: [PATCH V8 2/6] thermal: bcm2835: add thermal driver for bcm2835 soc\0"
+ "From\0edubezval@gmail.com (Eduardo Valentin)\0"
+ "Subject\0[PATCH V8 2/6] thermal: bcm2835: add thermal driver for bcm2835 soc\0"
  "Date\0Fri, 18 Nov 2016 20:22:25 -0800\0"
- "To\0kernel-TqfNSX0MhmxHKSADF0wUEw@public.gmane.org\0"
- "Cc\0Zhang Rui <rui.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>"
-  Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
-  Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>
-  Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
-  Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
-  Lee Jones <lee-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
-  Eric Anholt <eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
-  Russell King <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>
-  Florian Fainelli <f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
-  Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>
-  Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
-  linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-  devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-  linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
- " linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "Hello Martin,\n"
@@ -32,7 +16,7 @@
  "firmware/linux split is done in your platform. Still, one thing is not\n"
  "clear to me.\n"
  "\n"
- "On Fri, Nov 18, 2016 at 09:32:47AM +0100, kernel-TqfNSX0MhmxHKSADF0wUEw@public.gmane.org wrote:\n"
+ "On Fri, Nov 18, 2016 at 09:32:47AM +0100, kernel at martin.sperl.org wrote:\n"
  "> \n"
  "\n"
  "> The way that firmware works on the RPI is quite different from most others I guess.\n"
@@ -75,7 +59,7 @@
  "\n"
  "Who has the ownership of this device?\n"
  "\n"
- "> The above mentioned \342\200\234configuration if not running\342\200\235 reflect the values that\n"
+ "> The above mentioned ?configuration if not running? reflect the values that\n"
  "> the FW is currently setting. We should not change those values as long as the\n"
  "> Firmware is also reading the temperature on its own.\n"
  "\n"
@@ -105,7 +89,7 @@
  "> > it is clear to whoever reads in the future), then I would be OK with\n"
  "> > this driver. \n"
  "> \n"
- "> So how do you want this to get \342\200\234documented\342\200\235 in the driver?\n"
+ "> So how do you want this to get ?documented? in the driver?\n"
  "> The setup and Firmware is a generic feature of the SOC, so if we would put\n"
  "> some clarifications in this driver, then we would need to put it in every\n"
  "> bcm283X driver (which seems unreasonable).\n"
@@ -121,10 +105,6 @@
  "accessing this device.\n"
  "\n"
  "> Thanks,\n"
- "> \tMartin\n"
- "--\n"
- "To unsubscribe from this list: send the line \"unsubscribe devicetree\" in\n"
- "the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\n"
- More majordomo info at  http://vger.kernel.org/majordomo-info.html
+ "> \tMartin"
 
-4622242d5bb5d90157455995a97c8e4d1b3b16047d03cc4d1702abff36920637
+22bbf9304f6c6a0c1ffd90e2d72d69659a0f97f7eaa863cfb99a96d07641de95

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.