All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <1204281823.6243.78.camel@lappy>

diff --git a/a/1.txt b/N1/1.txt
index 78640d0..b19d11b 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -11,3 +11,9 @@ On Fri, 2008-02-29 at 16:55 +0800, Zhao Forrest wrote:
 
 No, rdtsc() goes directly to the hardware. You need a (preferably cheap)
 clock abstraction layer on top if you need this.
+
+
+-------------------------------------------------------------------------
+This SF.net email is sponsored by: Microsoft
+Defy all challenges. Microsoft(R) Visual Studio 2008.
+http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
diff --git a/a/content_digest b/N1/content_digest
index 7493405..6bdb9e4 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -3,8 +3,8 @@
  "Subject\0Re: Can Linux kernel handle unsynced TSC?\0"
  "Date\0Fri, 29 Feb 2008 11:43:43 +0100\0"
  "To\0Zhao Forrest <forrest.zhao@gmail.com>\0"
- "Cc\0linux-kernel@vger.kernel.org"
- " kvm-devel@lists.sourceforge.net\0"
+ "Cc\0kvm-devel@lists.sourceforge.net"
+ " linux-kernel@vger.kernel.org\0"
  "\00:1\0"
  "b\0"
  "\n"
@@ -19,6 +19,12 @@
  "> returned by the first rdtsc()?\n"
  "\n"
  "No, rdtsc() goes directly to the hardware. You need a (preferably cheap)\n"
- clock abstraction layer on top if you need this.
+ "clock abstraction layer on top if you need this.\n"
+ "\n"
+ "\n"
+ "-------------------------------------------------------------------------\n"
+ "This SF.net email is sponsored by: Microsoft\n"
+ "Defy all challenges. Microsoft(R) Visual Studio 2008.\n"
+ http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
 
-8a0b3f5c7f6e149a61079ae9b52adb9bac47e78dc9bd69ad51500e0fc3247414
+08c4d4b084b8858677c0fe85c9bd947050bf8222ea1f0f6eca963709716dddb5

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.