diff for duplicates of <4FFE4DD0.7020407@nvidia.com>

diff --git a/a/1.txt b/N1/1.txt
index f1bc804..4f79580 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -13,7 +13,8 @@ On Wednesday 11 July 2012 07:33 PM, Rob Herring 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:
@@ -24,7 +25,8 @@ On Wednesday 11 July 2012 07:33 PM, Rob Herring 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:
@@ -33,7 +35,7 @@ On Wednesday 11 July 2012 07:33 PM, Rob Herring 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>;
@@ -70,13 +72,13 @@ different voltages and this array covers all those 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>;
 > 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>;
 >>               };
@@ -123,6 +125,6 @@ I hope it explains the implementation.
 >>
 >> _______________________________________________
 >> 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
 >
diff --git a/a/content_digest b/N1/content_digest
index 9e96c15..24ab483 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,8 +1,8 @@
  "ref\04FFD77FE.8050206@nvidia.com\0"
  "ref\04FFD87BD.2030206@gmail.com\0"
- "From\0Prashant Gaikwad <pgaikwad@nvidia.com>\0"
- "Subject\0Re: Device tree binding for DVFS table\0"
- "Date\0Thu, 12 Jul 2012 04:20:48 +0000\0"
+ "From\0pgaikwad@nvidia.com (Prashant Gaikwad)\0"
+ "Subject\0Device tree binding for DVFS table\0"
+ "Date\0Thu, 12 Jul 2012 09:38:48 +0530\0"
  "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
@@ -21,7 +21,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"
@@ -32,7 +33,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"
@@ -41,7 +43,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"
@@ -78,13 +80,13 @@
  ">>\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"
  "> I don't see the point of repeating frequencies.\n"
  ">>               };\n"
- ">>               frequency-table@002 {\n"
+ ">>               frequency-table at 002 {\n"
  ">>                        reg =<0x002>;\n"
  ">>                        frequencies =<598 598 750 750 893 893 1000>;\n"
  ">>               };\n"
@@ -131,8 +133,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\n"
  >
 
-cb5dc74bf1ffbfbb3ac3563dc7b9993534c78213158eb700a77cdfa091d4ef55
+1c6fef3b5cc3828a33a34792f9a7afa2d40fe5900df6bf4962ee26872e9884ff
