All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <4FFD87BD.2030206@gmail.com>

diff --git a/a/1.txt b/N1/1.txt
index 5950729..b9ec9f0 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -12,7 +12,8 @@ On 07/11/2012 07:56 AM, Prashant Gaikwad wrote:
 > Following is the proposed binding for voltage and frequency tables used
 > in DVFS. Looking for comments/suggestions to make it generic.
 > 
-> ====DVFS table node=========> This node defines the voltage configuration for the DVFS which includes
+> =======DVFS table node===================
+> This node defines the voltage configuration for the DVFS which includes
 > the regulator and voltage array.
 > 
 > Required properties:
@@ -23,7 +24,8 @@ On 07/11/2012 07:56 AM, Prashant Gaikwad wrote:
 > #address-cells and #size-cells : To identify correct frequency table
 > using process id (or some other vendor specific way).
 > 
-> ====Frequency table node=======> 
+> ========Frequency table node===============
+> 
 > This node defines frequency configuration for the device DVFS.
 > 
 > Required properties:
@@ -32,7 +34,7 @@ On 07/11/2012 07:56 AM, Prashant Gaikwad wrote:
 > 
 > dvfs : the phandle for the DVFS table node
 > 
-> frequency-table@n
+> frequency-table at n
 >        reg = <n>; dependent on address-cells and size-cells in DVFS
 > table node.
 >        frequencies = <frequency array, values in MHz>;
@@ -63,7 +65,7 @@ The SOC is really characterized at all these voltages?
 > 
 > device {
 >              dvfs = <&cpu-dvfs-table>;
->              frequency-table@102 {
+>              frequency-table at 102 {
 >                       reg = <0x102>;
 >                       frequencies = <314 314 314 456 456 456 608 608 608
 > 760 817 817 912 1000>;
@@ -71,7 +73,7 @@ The SOC is really characterized at all these voltages?
 I don't see the point of repeating frequencies.
 
 >              };
->              frequency-table@002 {
+>              frequency-table at 002 {
 >                       reg = <0x002>;
 >                       frequencies = <598 598 750 750 893 893 1000>;
 >              };
@@ -90,5 +92,5 @@ Rob
 > 
 > _______________________________________________
 > linux-arm-kernel mailing list
-> linux-arm-kernel@lists.infradead.org
+> linux-arm-kernel at lists.infradead.org
 > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
\ No newline at end of file
diff --git a/a/content_digest b/N1/content_digest
index ae0e336..35fae68 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -2,13 +2,13 @@
   "ref\0004FFD77FE.8050206\@nvidia.com\0"
 ]
 [
-  "From\0Rob Herring <robherring2\@gmail.com>\0"
+  "From\0robherring2\@gmail.com (Rob Herring)\0"
 ]
 [
-  "Subject\0Re: Device tree binding for DVFS table\0"
+  "Subject\0Device tree binding for DVFS table\0"
 ]
 [
-  "Date\0Wed, 11 Jul 2012 14:03:41 +0000\0"
+  "Date\0Wed, 11 Jul 2012 09:03:41 -0500\0"
 ]
 [
   "To\0linux-arm-kernel\@lists.infradead.org\0"
@@ -34,7 +34,8 @@
   "> Following is the proposed binding for voltage and frequency tables used\n",
   "> in DVFS. Looking for comments/suggestions to make it generic.\n",
   "> \n",
-  "> ====DVFS table node=========> This node defines the voltage configuration for the DVFS which includes\n",
+  "> =======DVFS table node===================\n",
+  "> This node defines the voltage configuration for the DVFS which includes\n",
   "> the regulator and voltage array.\n",
   "> \n",
   "> Required properties:\n",
@@ -45,7 +46,8 @@
   "> #address-cells and #size-cells : To identify correct frequency table\n",
   "> using process id (or some other vendor specific way).\n",
   "> \n",
-  "> ====Frequency table node=======> \n",
+  "> ========Frequency table node===============\n",
+  "> \n",
   "> This node defines frequency configuration for the device DVFS.\n",
   "> \n",
   "> Required properties:\n",
@@ -54,7 +56,7 @@
   "> \n",
   "> dvfs : the phandle for the DVFS table node\n",
   "> \n",
-  "> frequency-table\@n\n",
+  "> frequency-table at n\n",
   ">        reg = <n>; dependent on address-cells and size-cells in DVFS\n",
   "> table node.\n",
   ">        frequencies = <frequency array, values in MHz>;\n",
@@ -85,7 +87,7 @@
   "> \n",
   "> device {\n",
   ">              dvfs = <&cpu-dvfs-table>;\n",
-  ">              frequency-table\@102 {\n",
+  ">              frequency-table at 102 {\n",
   ">                       reg = <0x102>;\n",
   ">                       frequencies = <314 314 314 456 456 456 608 608 608\n",
   "> 760 817 817 912 1000>;\n",
@@ -93,7 +95,7 @@
   "I don't see the point of repeating frequencies.\n",
   "\n",
   ">              };\n",
-  ">              frequency-table\@002 {\n",
+  ">              frequency-table at 002 {\n",
   ">                       reg = <0x002>;\n",
   ">                       frequencies = <598 598 750 750 893 893 1000>;\n",
   ">              };\n",
@@ -112,8 +114,8 @@
   "> \n",
   "> _______________________________________________\n",
   "> linux-arm-kernel mailing list\n",
-  "> linux-arm-kernel\@lists.infradead.org\n",
+  "> linux-arm-kernel at lists.infradead.org\n",
   "> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel"
 ]
 
-5d732e106671bbf96c145193a971f6f606981e310eb80ad8924809d104bdd6c2
+6aedcecd67da9ae90df0982d7b5a7d0fcc071b8d663f58bb7016fffbaeb0f0c5

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.