From: john stultz <johnstul@us.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 0/6] x86_64: Generic timekeeping for x86_64
Date: Tue, 08 Aug 2006 19:48:50 -0700 [thread overview]
Message-ID: <1155091730.13030.103.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <200608090441.27633.ak@suse.de>
On Wed, 2006-08-09 at 04:41 +0200, Andi Kleen wrote:
> On Wednesday 09 August 2006 04:17, john stultz wrote:
> > Hey Andi,
> > Just wanted to send this by as a first pass on the x86_64
> > generic timekeeping conversion. If you have the time, a quick review
> > and comments would be greatly appreciated.
>
> Ok, but it's more 2.6.20 material
Very much agreed! Just trying to get the ball rolling.
thanks
-john
prev parent reply other threads:[~2006-08-09 2:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 2:17 john stultz
2006-08-09 2:17 ` [RFC][PATCH 1/6] x86_64: Enable arch-generic vsyscall support john stultz
2006-08-09 2:29 ` Andi Kleen
2006-08-09 2:56 ` john stultz
2006-08-09 2:59 ` Andi Kleen
2006-08-09 2:17 ` [RFC][PATCH 2/6] x86_64: hpet_address cleanup john stultz
2006-08-09 2:31 ` Andi Kleen
2006-08-09 3:08 ` john stultz
2006-08-09 2:17 ` [RFC][PATCH 3/6] x86_64: Remove apic_runs_main_timer john stultz
2006-08-09 2:31 ` Andi Kleen
2006-08-09 2:17 ` [RFC][PATCH 4/6] x86_64: Enable CONFIG_GENERIC_TIME john stultz
2006-08-09 2:17 ` [RFC][PATCH 5/6] x86_64: Clocksources for x86-64 john stultz
2006-08-09 2:41 ` Andi Kleen
2006-08-09 3:41 ` john stultz
2006-08-09 2:17 ` [RFC][PATCH 6/6] x86_64: GENERIC_TIME based vsyscall code john stultz
2006-08-09 2:45 ` Andi Kleen
2006-08-09 2:41 ` [RFC][PATCH 0/6] x86_64: Generic timekeeping for x86_64 Andi Kleen
2006-08-09 2:48 ` john stultz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1155091730.13030.103.camel@cog.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®