From: tony@bakeyournoodle.com (Tony Breeds)
To: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Realtime Kernel <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH 1/5] Implement {read,update}_persistent_clock.
Date: Wed, 19 Sep 2007 16:53:29 +1000 [thread overview]
Message-ID: <20070919065329.GU9814@bakeyournoodle.com> (raw)
In-Reply-To: <1190184586.867449.381310088392.qpush@thor>
On Wed, Sep 19, 2007 at 04:49:46PM +1000, Tony Breeds wrote:
> With these functions implemented we cooperate better with the generic
> timekeeping code. This obsoletes the need for the timer sysdev as a bonus.
I should have added that this patch series applies on top of Benh's 601
fixes.
Yours Tony
linux.conf.au http://linux.conf.au/ || http://lca2008.linux.org.au/
Jan 28 - Feb 02 2008 The Australian Linux Technical Conference!
prev parent reply other threads:[~2007-09-19 6:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 6:49 [PATCH 1/5] Implement {read,update}_persistent_clock Tony Breeds
2007-09-19 6:49 ` [PATCH 3/5] Implement clockevents driver for powerpc Tony Breeds
2007-09-19 6:49 ` [PATCH 4/5] Include hrtimer.h in tick.h Tony Breeds
2007-09-19 6:49 ` [PATCH 2/5] Implement generic time of day clocksource for powerpc machines Tony Breeds
2007-09-19 15:43 ` Daniel Walker
2007-09-19 15:43 ` Daniel Walker
2007-09-20 0:52 ` Paul Mackerras
2007-09-20 0:52 ` Paul Mackerras
2007-09-20 1:35 ` Daniel Walker
2007-09-20 1:35 ` Daniel Walker
2007-09-20 1:46 ` Paul Mackerras
2007-09-20 1:46 ` Paul Mackerras
2007-09-20 1:54 ` Daniel Walker
2007-09-20 1:54 ` Daniel Walker
2007-09-20 3:29 ` David Gibson
2007-09-20 3:29 ` David Gibson
2007-09-20 3:38 ` Daniel Walker
2007-09-20 3:38 ` Daniel Walker
2007-09-20 16:35 ` john stultz
2007-09-20 16:35 ` john stultz
2007-09-20 23:46 ` Tony Breeds
2007-09-20 23:46 ` Tony Breeds
2007-09-19 6:49 ` [PATCH 5/5] Enable tickless idle and high res timers for powerpc Tony Breeds
2007-09-19 6:53 ` Tony Breeds [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=20070919065329.GU9814@bakeyournoodle.com \
--to=tony@bakeyournoodle.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
/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 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.