All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <4E087859.5010901@cam.ac.uk>

diff --git a/a/1.txt b/N1/1.txt
index eec2f09..4859dc6 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -3,10 +3,10 @@ On 06/25/11 21:10, Koen Kooi wrote:
 > Op 25 jun 2011, om 20:51 heeft Premi, Sanjeev het volgende geschreven:
 > 
 >>> -----Original Message-----
->>> From: linux-omap-owner@vger.kernel.org 
->>> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Koen Kooi
+>>> From: linux-omap-owner at vger.kernel.org 
+>>> [mailto:linux-omap-owner at vger.kernel.org] On Behalf Of Koen Kooi
 >>> Sent: Saturday, June 25, 2011 1:47 PM
->>> To: linux-omap@vger.kernel.org List
+>>> To: linux-omap at vger.kernel.org List
 >>> Cc: linux-arm-kernel; Paul Walmsley
 >>> Subject: Re: [PATCH] omap3: beagle: Use GPTIMERi 1 for clockevents
 >>>
@@ -39,7 +39,7 @@ On 06/25/11 21:10, Koen Kooi wrote:
 >>     many Beagleboards where current code is necessary.
 > 
 
-> I get a value of 1010 ±10 bogoMIPS consistently with .39 + dvfs
+> I get a value of 1010 ?10 bogoMIPS consistently with .39 + dvfs
 > patches. Having said that, this patch does seem to be an improvement,
 > but has it actually been tested on real beagleboard hardware with a
 > recent kernel? Especially on the boards affected by the capacitor
diff --git a/a/content_digest b/N1/content_digest
index 636fb6d..7813d96 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -2,13 +2,10 @@
  "ref\086CFE860-E18E-4B96-A753-11EB7C5C1C86@dominion.thruhere.net\0"
  "ref\0B85A65D85D7EB246BE421B3FB0FBB593024D6C2FE2@dbde02.ent.ti.com\0"
  "ref\0DE79F8F5-7D8A-46B8-8C8C-C2A7515E9117@dominion.thruhere.net\0"
- "From\0Jonathan Cameron <jic23@cam.ac.uk>\0"
- "Subject\0Re: [PATCH] omap3: beagle: Use GPTIMERi 1 for clockevents\0"
+ "From\0jic23@cam.ac.uk (Jonathan Cameron)\0"
+ "Subject\0[PATCH] omap3: beagle: Use GPTIMERi 1 for clockevents\0"
  "Date\0Mon, 27 Jun 2011 13:32:25 +0100\0"
- "To\0Koen Kooi <koen@dominion.thruhere.net>\0"
- "Cc\0Paul Walmsley <paul@pwsan.com>"
-  linux-omap@vger.kernel.org List <linux-omap@vger.kernel.org>
- " linux-arm-kernel <linux-arm-kernel@lists.infradead.org>\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "On 06/25/11 21:10, Koen Kooi wrote:\n"
@@ -16,10 +13,10 @@
  "> Op 25 jun 2011, om 20:51 heeft Premi, Sanjeev het volgende geschreven:\n"
  "> \n"
  ">>> -----Original Message-----\n"
- ">>> From: linux-omap-owner@vger.kernel.org \n"
- ">>> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Koen Kooi\n"
+ ">>> From: linux-omap-owner at vger.kernel.org \n"
+ ">>> [mailto:linux-omap-owner at vger.kernel.org] On Behalf Of Koen Kooi\n"
  ">>> Sent: Saturday, June 25, 2011 1:47 PM\n"
- ">>> To: linux-omap@vger.kernel.org List\n"
+ ">>> To: linux-omap at vger.kernel.org List\n"
  ">>> Cc: linux-arm-kernel; Paul Walmsley\n"
  ">>> Subject: Re: [PATCH] omap3: beagle: Use GPTIMERi 1 for clockevents\n"
  ">>>\n"
@@ -52,7 +49,7 @@
  ">>     many Beagleboards where current code is necessary.\n"
  "> \n"
  "\n"
- "> I get a value of 1010 \302\26110 bogoMIPS consistently with .39 + dvfs\n"
+ "> I get a value of 1010 ?10 bogoMIPS consistently with .39 + dvfs\n"
  "> patches. Having said that, this patch does seem to be an improvement,\n"
  "> but has it actually been tested on real beagleboard hardware with a\n"
  "> recent kernel? Especially on the boards affected by the capacitor\n"
@@ -69,4 +66,4 @@
  "\n"
  Jonathan
 
-4f2d0e959d02e5d2e0b6d75c2f534373cc3a7894e9b63ccab13d84258064cb94
+9077c914060efe387ee4f2ba4d49cbab8f2556070ac26ec65955e522d81ccecb

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.