All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <53BCF463.3000604@linaro.org>

diff --git a/a/1.txt b/N1/1.txt
index 4780142..299333c 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -11,7 +11,7 @@ On 08/07/14 21:00, Stephen Boyd wrote:
 > these drivers end up having an extra reg property (or two) that points
 > to a register in the efuse and some length, i.e you see this:
 >
-> 	thermal-sensor@34000 {
+> 	thermal-sensor at 34000 {
 > 		compatible = "sensor";
 > 		reg = <0x34000 0x1000>, <0x10018 0xc>;
 > 		reg-names = "sensor", "efuse_calib";
@@ -20,12 +20,12 @@ On 08/07/14 21:00, Stephen Boyd wrote:
 >
 > I imagine in DT we want something more like this:
 >
-> 	efuse: efuse@10000 {
+> 	efuse: efuse at 10000 {
 > 		compatible = "efuse";
 > 		reg = <0x10000 0x1000>;
 > 	}
 >
-> 	thermal-sensor@34000 {
+> 	thermal-sensor at 34000 {
 > 		compatible = "sensor";
 > 		reg = <0x34000 0x1000>;
 > 		efuse = <&efuse 0x18>;
@@ -56,12 +56,12 @@ this:  https://lkml.org/lkml/2013/7/5/361
 
 Something like this:
 
-	efuse: efuse@10000 {
+	efuse: efuse at 10000 {
   		compatible = "efuse", "syscon";
   		reg = <0x10000 0x1000>;
   	}
 
-  	thermal-sensor@34000 {
+  	thermal-sensor at 34000 {
   		compatible = "sensor", "soc-xyz";
   		reg = <0x34000 0x1000>;
 		syscon = <&efuse>;
diff --git a/a/content_digest b/N1/content_digest
index f1f2c34..8ffb8c8 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,16 +1,8 @@
  "ref\053BC4DD7.20906@codeaurora.org\0"
- "From\0Srinivas Kandagatla <srinivas.kandagatla@linaro.org>\0"
- "Subject\0Re: a case for a common efuse API?\0"
+ "From\0srinivas.kandagatla@linaro.org (Srinivas Kandagatla)\0"
+ "Subject\0a case for a common efuse API?\0"
  "Date\0Wed, 09 Jul 2014 08:50:59 +0100\0"
- "To\0Stephen Boyd <sboyd@codeaurora.org>"
- " linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>\0"
- "Cc\0Linux Kernel Mailing List <linux-kernel@vger.kernel.org>"
-  Bjorn Andersson <bjorn.andersson@sonymobile.com>
-  Stephen Warren <swarren@nvidia.com>
-  Peter De Schrijver <pdeschrijver@nvidia.com>
-  Arnd Bergmann <arnd@arndb.de>
-  linux-arm-msm@vger.kernel.org <linux-arm-msm@vger.kernel.org>
- " devicetree@vger.kernel.org <devicetree@vger.kernel.org>\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "\n"
@@ -26,7 +18,7 @@
  "> these drivers end up having an extra reg property (or two) that points\n"
  "> to a register in the efuse and some length, i.e you see this:\n"
  ">\n"
- "> \tthermal-sensor@34000 {\n"
+ "> \tthermal-sensor at 34000 {\n"
  "> \t\tcompatible = \"sensor\";\n"
  "> \t\treg = <0x34000 0x1000>, <0x10018 0xc>;\n"
  "> \t\treg-names = \"sensor\", \"efuse_calib\";\n"
@@ -35,12 +27,12 @@
  ">\n"
  "> I imagine in DT we want something more like this:\n"
  ">\n"
- "> \tefuse: efuse@10000 {\n"
+ "> \tefuse: efuse at 10000 {\n"
  "> \t\tcompatible = \"efuse\";\n"
  "> \t\treg = <0x10000 0x1000>;\n"
  "> \t}\n"
  ">\n"
- "> \tthermal-sensor@34000 {\n"
+ "> \tthermal-sensor at 34000 {\n"
  "> \t\tcompatible = \"sensor\";\n"
  "> \t\treg = <0x34000 0x1000>;\n"
  "> \t\tefuse = <&efuse 0x18>;\n"
@@ -71,12 +63,12 @@
  "\n"
  "Something like this:\n"
  "\n"
- "\tefuse: efuse@10000 {\n"
+ "\tefuse: efuse at 10000 {\n"
  "  \t\tcompatible = \"efuse\", \"syscon\";\n"
  "  \t\treg = <0x10000 0x1000>;\n"
  "  \t}\n"
  "\n"
- "  \tthermal-sensor@34000 {\n"
+ "  \tthermal-sensor at 34000 {\n"
  "  \t\tcompatible = \"sensor\", \"soc-xyz\";\n"
  "  \t\treg = <0x34000 0x1000>;\n"
  "\t\tsyscon = <&efuse>;\n"
@@ -96,4 +88,4 @@
  "> attribute that may or may not be in use by some userspace code.\n"
  >
 
-88f21862e4bc233351e73c80ce5034a0c050051fbfa48f80fa69d11e10e6c8db
+110b5c2faa1c609de726e070a76645f84e28f8283ec4148a244e571e6fbea6fd

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.