diff for duplicates of <556438FF.7020105@linaro.org>

diff --git a/a/1.txt b/N1/1.txt
index d33425e..7f66f6e 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -24,11 +24,11 @@ Ok,
 > Take for instance the case where you have multiple slot accessing different EEPROMs.
 >
 >> slots {
->> 	slot@0 {
+>> 	slot at 0 {
 >> 		eeprom = <&cape0_data>;
 >> 	};
 >>
->> 	slot@1 {
+>> 	slot at 1 {
 >> 		eeprom = <&cape1_data>;
 >> 	};
 >> };
@@ -38,9 +38,9 @@ Do you expect to have more properties associated with each slot in future?
 Or is it just to get hold of eeprom data?
 
 >
-> In that case there is no per-device node mapping; it’s a per-sub node.
+> In that case there is no per-device node mapping; it?s a per-sub node.
 >
-> For now I’m exporting the of_* accessors again, please consider exposing the of_* API again.
+> For now I?m exporting the of_* accessors again, please consider exposing the of_* API again.
 Sure, we can export of_nvmem_cell_get symbol for usecases like this.
 
 Having said that, I got one comment on the way the nvmem is used in your 
@@ -62,10 +62,5 @@ We can work on how to get the of_*based once you decide to move to this api.
 >
 > Regards
 >
-> — Pantelis
+> ? Pantelis
 >
-
-_______________________________________________
-linux-arm-kernel mailing list
-linux-arm-kernel@lists.infradead.org
-http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
diff --git a/a/content_digest b/N1/content_digest
index a109bfc..2eaaa95 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,24 +1,10 @@
  "ref\01427752492-17039-1-git-send-email-srinivas.kandagatla@linaro.org\0"
  "ref\01432226535-8640-1-git-send-email-srinivas.kandagatla@linaro.org\0"
  "ref\0E5772084-6CF5-41DE-B68B-073D9F75F0BC@konsulko.com\0"
- "From\0Srinivas Kandagatla <srinivas.kandagatla@linaro.org>\0"
- "Subject\0Re: [PATCH v5 00/11] Add simple NVMEM Framework via regmap.\0"
+ "From\0srinivas.kandagatla@linaro.org (Srinivas Kandagatla)\0"
+ "Subject\0[PATCH v5 00/11] Add simple NVMEM Framework via regmap.\0"
  "Date\0Tue, 26 May 2015 10:12:31 +0100\0"
- "To\0Pantelis Antoniou <pantelis.antoniou@konsulko.com>\0"
- "Cc\0linux-arm-msm@vger.kernel.org"
-  devicetree <devicetree@vger.kernel.org>
-  Arnd Bergmann <arnd@arndb.de>
-  Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-  Sascha Hauer <s.hauer@pengutronix.de>
-  sboyd@codeaurora.org
-  Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
-  Rob Herring <robh+dt@kernel.org>
-  Mark Brown <broonie@kernel.org>
-  Kumar Gala <galak@codeaurora.org>
-  Matt Porter <mporter@konsulko.com>
-  Maxime Ripard <maxime.ripard@free-electrons.com>
-  linux-api@vger.kernel.org
- " linux-arm-kernel@lists.infradead.org\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "Hi Pantelis,\n"
@@ -47,11 +33,11 @@
  "> Take for instance the case where you have multiple slot accessing different EEPROMs.\n"
  ">\n"
  ">> slots {\n"
- ">> \tslot@0 {\n"
+ ">> \tslot at 0 {\n"
  ">> \t\teeprom = <&cape0_data>;\n"
  ">> \t};\n"
  ">>\n"
- ">> \tslot@1 {\n"
+ ">> \tslot at 1 {\n"
  ">> \t\teeprom = <&cape1_data>;\n"
  ">> \t};\n"
  ">> };\n"
@@ -61,9 +47,9 @@
  "Or is it just to get hold of eeprom data?\n"
  "\n"
  ">\n"
- "> In that case there is no per-device node mapping; it\342\200\231s a per-sub node.\n"
+ "> In that case there is no per-device node mapping; it?s a per-sub node.\n"
  ">\n"
- "> For now I\342\200\231m exporting the of_* accessors again, please consider exposing the of_* API again.\n"
+ "> For now I?m exporting the of_* accessors again, please consider exposing the of_* API again.\n"
  "Sure, we can export of_nvmem_cell_get symbol for usecases like this.\n"
  "\n"
  "Having said that, I got one comment on the way the nvmem is used in your \n"
@@ -85,12 +71,7 @@
  ">\n"
  "> Regards\n"
  ">\n"
- "> \342\200\224 Pantelis\n"
- ">\n"
- "\n"
- "_______________________________________________\n"
- "linux-arm-kernel mailing list\n"
- "linux-arm-kernel@lists.infradead.org\n"
- http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
+ "> ? Pantelis\n"
+ >
 
-3cdc8e7694eada9bde2990623b0ff57de2ccb9cba9651e1edf0449118b848c06
+e8ce550f4b1e7d011d13831787ead91bca705a8b714693c6857619df934833fe
