diff for duplicates of <20130625204726.BF65C12647A@dev.laptop.org>

diff --git a/a/1.txt b/N1/1.txt
index 61afce0..640128c 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -24,7 +24,7 @@ Ordered roughly from highest to lowest importance:
 The OLPC XO boots entirely from the device tree, all clocks and things are
 defined there. Your current display controller driver is close to
 DT-compatibility, the only tricky bit is:
-?? ?? ?? ?? ?? ?? ?? ??clk = clk_get_sys("dovefb.0", "extclk");
+Â  Â  Â  Â  Â  Â  Â  Â clk = clk_get_sys("dovefb.0", "extclk");
 
 Not sure how that would translate to DT, or if we can transform that into
 something that works for both DT and platform devices. The norm in DT is
@@ -51,7 +51,7 @@ connector/encoder which would then appear later.
 Already found a couple of register conflicts between your dove and the MMP
 platforms. Your LCD_SPU_ADV_REG is something completely different here.
 
-The high bits of the DMA_CTRL0 register is used to select a clock. ??In the
+The high bits of the DMA_CTRL0 register is used to select a clock. Â In the
 dove and MMP2 case these bits are 31:30 but on MMP3 this is 31:29. Also, OLPC
 uses this field to select the LCD clock as a clock source, but your driver
 chooses another clock for cubox. So we need ways to represent all of these
@@ -107,7 +107,7 @@ On MMP2/MMP3 the situation is a bit different. 3 output paths are supported
 SoC, no separate encoder chip necessary).
 
 These paths are closely related, probably not as far separated as your
-"dual CRTC" dove model. ??For example, up to 9 overlays are supported, but if
+"dual CRTC" dove model. Â For example, up to 9 overlays are supported, but if
 you have 6 of them running on the TV path then you only have 3 available for
 use on the panel path. If you only activate one path then you can use all 9
 there. etc.
diff --git a/N1/2.hdr b/N1/2.hdr
new file mode 100644
index 0000000..4b86001
--- /dev/null
+++ b/N1/2.hdr
@@ -0,0 +1,4 @@
+Content-Type: text/plain; charset="us-ascii"
+MIME-Version: 1.0
+Content-Transfer-Encoding: 7bit
+Content-Disposition: inline
diff --git a/N1/2.txt b/N1/2.txt
new file mode 100644
index 0000000..8133cf0
--- /dev/null
+++ b/N1/2.txt
@@ -0,0 +1,4 @@
+_______________________________________________
+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 a051c9f..7386599 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,8 +1,10 @@
- "From\0dsd@laptop.org (Daniel Drake)\0"
+ "From\0Daniel Drake <dsd@laptop.org>\0"
  "Subject\0Armada DRM driver on OLPC XO\0"
  "Date\0Tue, 25 Jun 2013 16:47:26 -0400 (EDT)\0"
- "To\0linux-arm-kernel@lists.infradead.org\0"
- "\00:1\0"
+ "To\0linux@arm.linux.org.uk\0"
+ "Cc\0dri-devel@lists.freedesktop.org"
+ " linux-arm-kernel@lists.infradead.org\0"
+ "\01:1\0"
  "b\0"
  "Hi Russell,\n"
  "\n"
@@ -30,7 +32,7 @@
  "The OLPC XO boots entirely from the device tree, all clocks and things are\n"
  "defined there. Your current display controller driver is close to\n"
  "DT-compatibility, the only tricky bit is:\n"
- "?? ?? ?? ?? ?? ?? ?? ??clk = clk_get_sys(\"dovefb.0\", \"extclk\");\n"
+ "\303\202\302\240 \303\202\302\240 \303\202\302\240 \303\202\302\240 \303\202\302\240 \303\202\302\240 \303\202\302\240 \303\202\302\240clk = clk_get_sys(\"dovefb.0\", \"extclk\");\n"
  "\n"
  "Not sure how that would translate to DT, or if we can transform that into\n"
  "something that works for both DT and platform devices. The norm in DT is\n"
@@ -57,7 +59,7 @@
  "Already found a couple of register conflicts between your dove and the MMP\n"
  "platforms. Your LCD_SPU_ADV_REG is something completely different here.\n"
  "\n"
- "The high bits of the DMA_CTRL0 register is used to select a clock. ??In the\n"
+ "The high bits of the DMA_CTRL0 register is used to select a clock. \303\202\302\240In the\n"
  "dove and MMP2 case these bits are 31:30 but on MMP3 this is 31:29. Also, OLPC\n"
  "uses this field to select the LCD clock as a clock source, but your driver\n"
  "chooses another clock for cubox. So we need ways to represent all of these\n"
@@ -113,7 +115,7 @@
  "SoC, no separate encoder chip necessary).\n"
  "\n"
  "These paths are closely related, probably not as far separated as your\n"
- "\"dual CRTC\" dove model. ??For example, up to 9 overlays are supported, but if\n"
+ "\"dual CRTC\" dove model. \303\202\302\240For example, up to 9 overlays are supported, but if\n"
  "you have 6 of them running on the TV path then you only have 3 available for\n"
  "use on the panel path. If you only activate one path then you can use all 9\n"
  "there. etc.\n"
@@ -460,5 +462,11 @@
  "+module_platform_driver(dumb_driver);\n"
  "-- \n"
  1.8.1.4
+ "\01:2\0"
+ "b\0"
+ "_______________________________________________\n"
+ "linux-arm-kernel mailing list\n"
+ "linux-arm-kernel@lists.infradead.org\n"
+ http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
 
-1a4d93f08251eaa01fb98f73ab14d424171d6866395db76a941f70850ab3adf6
+852b7a47ac356f989cda22d259d1478d0299ff6b847abaeb0b58423beb34da9f
