public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
	george@wildturkeyranch.net, Steven Rostedt <rostedt@goodmis.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ulrich Windl <ulrich.windl@rz.uni-regensburg.de>,
	Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCHSET 0/10] Time: Generic Timekeeping (v.C1)
Date: Thu, 23 Mar 2006 11:40:34 -0800	[thread overview]
Message-ID: <1143142835.2661.7.camel@leatherman> (raw)
In-Reply-To: <Pine.LNX.4.64.0603231209380.17704@scrub.home>

On Thu, 2006-03-23 at 13:48 +0100, Roman Zippel wrote:
> Hi,
> 
> On Wed, 22 Mar 2006, john stultz wrote:
> 
> > Andrew, All,
> > 	Here is an updated version of the smaller, reworked and 
> > improved patchset I mailed out monday. Please consider for inclusion 
> > into your tree.
> 
> It looks pretty good already. :)

</me rubs his eyes and reads that again>

> Give me a bit of time to rework the middle part a bit and if we can agree 
> to make the new gettimeofday functions optional for an arch, IMO it would 
> be ok for 2.6.17. 

? The new gettimeofday functions are optional. Don't enable
CONFIG_GENERIC_TIME and you're good to go. Could you clarify what you
mean?

> I think the important part is to get the generic clock 
> infrastructure merged, so it can be used by other kernel parts, the 
> unification of performance sensitive parts can still be done on top of it 
> a bit later.

Ok, I'm still not sure how you intend to you the clocksource bits
outside of timekeeping, but I'm interested in hearing about it.

thanks
-john


      parent reply	other threads:[~2006-03-23 19:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-23  3:05 [PATCHSET 0/10] Time: Generic Timekeeping (v.C1) john stultz
2006-03-23  3:05 ` [PATCH 1/10] Time: Clocksource Infrastructure john stultz
2006-03-23  3:06 ` [PATCH 2/10] Time: Use clocksource infrastructure for update_wall_time john stultz
2006-03-23  3:06 ` [PATCH 3/10] Time: Let user request precision from current_tick_length() john stultz
2006-03-23  3:06 ` [PATCH 4/10] Time: Use clocksource abstraction for NTP adjustments john stultz
2006-03-23  3:06 ` [PATCH 5/10] Time: Introduce arch generic time accessors john stultz
2006-03-23  3:06 ` [PATCH 6/10] Time: i386 Conversion - part 1: Move timer_pit.c to i8253.c john stultz
2006-03-23  3:06 ` [PATCH 7/10] Time: i386 Conversion - part 2: Rework TSC Support john stultz
2006-03-23  3:06 ` [PATCH 8/10] Time: i386 Conversion - part 3: Enable Generic Timekeeping john stultz
2006-03-23  3:06 ` [PATCH 9/10] Time: i386 Conversion - part 4: Remove Old timer_opts Code john stultz
2006-03-23  3:06 ` [PATCH 10/10] Time: i386 Clocksource Drivers john stultz
2006-03-23 12:48 ` [PATCHSET 0/10] Time: Generic Timekeeping (v.C1) Roman Zippel
2006-03-23 14:20   ` Thomas Gleixner
2006-03-23 13:45     ` Roman Zippel
2006-03-23 19:40   ` 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=1143142835.2661.7.camel@leatherman \
    --to=johnstul@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=george@wildturkeyranch.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=ulrich.windl@rz.uni-regensburg.de \
    --cc=zippel@linux-m68k.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