All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <55009515.2010404@ti.com>

diff --git a/a/1.txt b/N1/1.txt
index f98b9ad..0f70d1c 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -5,7 +5,7 @@ On 03/11/2015 12:32 PM, Tony Lindgren wrote:
 >>>> Suman and I have been looking at this together, so I can comment here. An
 >>>> implementation like this is what Suman is referring to:
 >>>>
->>>> +               l4_wkup: l4_wkup@44c00000 {
+>>>> +               l4_wkup: l4_wkup at 44c00000 {
 >>>> +                       compatible = "am335-l4-wkup", "simple-bus";
 >>>> +                       #address-cells = <2>;
 >>>> +                       #size-cells = <1>;
@@ -22,7 +22,7 @@ On 03/11/2015 12:32 PM, Tony Lindgren wrote:
 >> and the M3 DMEM entry below will be adjusted as <1 0x80000 0x2000>.
 >>
 >>>> +
->>>> +                       wkup_m3: wkup_m3@1,0 {
+>>>> +                       wkup_m3: wkup_m3 at 1,0 {
 >>>> +                               compatible = "ti,am3353-wkup-m3";
 >>>> +                               reg = <1 0x0     0x4000>,       /* M3 UMEM */
 >>>> +                                     <2 0x80000 0x2000>;       /* M3 DMEM */
@@ -34,7 +34,7 @@ On 03/11/2015 12:32 PM, Tony Lindgren wrote:
 >>>> +
 >>>>
 >>>> The of_* layer automatically translates everything so the pdata-quirks can still
->>>> match based on wkup_m3@44d00000. The existing wkup_m3_rproc driver works almost
+>>>> match based on wkup_m3 at 44d00000. The existing wkup_m3_rproc driver works almost
 >>>> entirely as is with this, all cpu addresses are read and mapped correctly but
 >>>> the driver no longer will read the actual device addresses correctly which we
 >>>> need for understanding where to load the firmware sections.
diff --git a/a/content_digest b/N1/content_digest
index 75339b5..b8ca1d6 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -9,18 +9,10 @@
  "ref\020150311162635.GZ5264@atomide.com\0"
  "ref\0550078D5.7080700@ti.com\0"
  "ref\020150311173212.GC5264@atomide.com\0"
- "From\0Suman Anna <s-anna@ti.com>\0"
- "Subject\0Re: [PATCH v2 2/2] ARM: dts: am33xx: Move wkup_m3 node to soc node and add ranges\0"
+ "From\0s-anna@ti.com (Suman Anna)\0"
+ "Subject\0[PATCH v2 2/2] ARM: dts: am33xx: Move wkup_m3 node to soc node and add ranges\0"
  "Date\0Wed, 11 Mar 2015 14:18:45 -0500\0"
- "To\0Tony Lindgren <tony@atomide.com>\0"
- "Cc\0Dave Gerlach <d-gerlach@ti.com>"
-  linux-arm-kernel@lists.infradead.org
-  linux-kernel@vger.kernel.org
-  linux-omap@vger.kernel.org
-  devicetree@vger.kernel.org
-  Ohad Ben-Cohen <ohad@wizery.com>
-  Kevin Hilman <khilman@linaro.org>
- " Felipe Balbi <balbi@ti.com>\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "On 03/11/2015 12:32 PM, Tony Lindgren wrote:\n"
@@ -30,7 +22,7 @@
  ">>>> Suman and I have been looking at this together, so I can comment here. An\n"
  ">>>> implementation like this is what Suman is referring to:\n"
  ">>>>\n"
- ">>>> +               l4_wkup: l4_wkup@44c00000 {\n"
+ ">>>> +               l4_wkup: l4_wkup at 44c00000 {\n"
  ">>>> +                       compatible = \"am335-l4-wkup\", \"simple-bus\";\n"
  ">>>> +                       #address-cells = <2>;\n"
  ">>>> +                       #size-cells = <1>;\n"
@@ -47,7 +39,7 @@
  ">> and the M3 DMEM entry below will be adjusted as <1 0x80000 0x2000>.\n"
  ">>\n"
  ">>>> +\n"
- ">>>> +                       wkup_m3: wkup_m3@1,0 {\n"
+ ">>>> +                       wkup_m3: wkup_m3 at 1,0 {\n"
  ">>>> +                               compatible = \"ti,am3353-wkup-m3\";\n"
  ">>>> +                               reg = <1 0x0     0x4000>,       /* M3 UMEM */\n"
  ">>>> +                                     <2 0x80000 0x2000>;       /* M3 DMEM */\n"
@@ -59,7 +51,7 @@
  ">>>> +\n"
  ">>>>\n"
  ">>>> The of_* layer automatically translates everything so the pdata-quirks can still\n"
- ">>>> match based on wkup_m3@44d00000. The existing wkup_m3_rproc driver works almost\n"
+ ">>>> match based on wkup_m3 at 44d00000. The existing wkup_m3_rproc driver works almost\n"
  ">>>> entirely as is with this, all cpu addresses are read and mapped correctly but\n"
  ">>>> the driver no longer will read the actual device addresses correctly which we\n"
  ">>>> need for understanding where to load the firmware sections.\n"
@@ -101,4 +93,4 @@
  "regards\n"
  Suman
 
-27b81823e315fbbe3f05a8e8ee82c321bf54667aa8fb53b7dbc22b09d8c35dc7
+a0963c73a28f8709c1f844df395143cfa61aee7dfda018711c2408d1e3762d3e

diff --git a/a/content_digest b/N2/content_digest
index 75339b5..90ce0b9 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -14,10 +14,10 @@
  "Date\0Wed, 11 Mar 2015 14:18:45 -0500\0"
  "To\0Tony Lindgren <tony@atomide.com>\0"
  "Cc\0Dave Gerlach <d-gerlach@ti.com>"
-  linux-arm-kernel@lists.infradead.org
-  linux-kernel@vger.kernel.org
-  linux-omap@vger.kernel.org
-  devicetree@vger.kernel.org
+  <linux-arm-kernel@lists.infradead.org>
+  <linux-kernel@vger.kernel.org>
+  <linux-omap@vger.kernel.org>
+  <devicetree@vger.kernel.org>
   Ohad Ben-Cohen <ohad@wizery.com>
   Kevin Hilman <khilman@linaro.org>
  " Felipe Balbi <balbi@ti.com>\0"
@@ -101,4 +101,4 @@
  "regards\n"
  Suman
 
-27b81823e315fbbe3f05a8e8ee82c321bf54667aa8fb53b7dbc22b09d8c35dc7
+82a2e0e8fcc8f4a60b79392b49a3dd4dcd7df3f94080fdd9847bfc1ceceea5c6

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.